YEA!!! Auth_service passed testing. Miriam On 8/19/13 10:42 AM, "Shane Canon" <[email protected]> wrote:
Miriam,
Can you try now? I think the errors were related to the testing of Mongo replication.
--Shane
On Aug 19, 2013, at 6:22 AM, "Land, Miriam L." <[email protected]> wrote:
Shane,
The 'make test' for auth_service still ends in 'FAILED'. Am I reading the results right? Am I doing something wrong?
Miriam
--------------------------------- make test Makefile:53: warning: overriding commands for target `build-docs' Makefile:49: warning: ignoring old commands for target `build-docs' cd authorization_server; \ ./manage.py test authorization_server No connection settings specified: 'Settings' object has no attribute 'MONGODB_CONN' Connection to mongodb.kbase.us by default. WARNING:root:MongoDB is a read-only instance, no roles can be created, updated or deleted Creating test database for alias 'default'... No connection settings specified: 'Settings' object has no attribute 'MONGODB_CONN'
sNo connection settings specified: 'Settings' object has no attribute 'MONGODB_CONN'
sNo connection settings specified: 'Settings' object has no attribute 'MONGODB_CONN'
FNo connection settings specified: 'Settings' object has no attribute 'MONGODB_CONN'
s ====================================================================== FAIL: testRead (authorization_server.tests.RoleHandlerTest) ---------------------------------------------------------------------- Traceback (most recent call last): File
"/kb/dev_container/modules/auth_service/authorization_server/authorizatio n_ server/tests.py", line 252, in testRead self.assertEqual(resp.status_code, 200, "Should accept queries from legit kbase test user") AssertionError: Should accept queries from legit kbase test user
---------------------------------------------------------------------- Ran 4 tests in 0.495s
FAILED (failures=1, skipped=3) Destroying test database for alias 'default'... make: *** [test_django] Error 1
On 8/17/13 1:25 PM, "Shane Canon" <[email protected]> wrote:
Miriam,
Shock is deployed now. It still has one minor fix that is required, but we can work through those during deployment.
--Shane