Issue 1048303
Created on 2004-10-16 13:15 by a1s, last changed 2004-10-16 13:15 by a1s.
msg1490 |
Author: [hidden] (a1s) |
Date: 2004-10-16 13:15 |
|
FAIL: test_modifyClass
(test.test_metakit.metakitSchemaTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "E:\usr\src\roundup-0.7\.\test\db_test_base.py",
line 1224, in test_modifyClass
self.assertEqual(self.db.a.get(aid, 'newnum'), None)
File "E:\Python23\lib\unittest.py", line 302, in
failUnlessEqual
raise self.failureException, \
AssertionError: 0 != None
(in 0.8, 0.0 != None).
this is documented behaviour for metakit backend if
BACKWARDS_COMPATIBLE is set (default).
test case needs to be fixed. better yet, both
BACKWARDS_COMPATIBLE and not BACKWARDS_COMPATIBLE modes
should be tested.
discussion: change default setting to disable
compatibility mode?
|
msg1491 |
Author: [hidden] (a1s) |
Date: 2004-10-16 13:22 |
|
Logged In: YES
user_id=8719
at the least, we may move 'newnum' test at the end of test
case to have it fail after all other tests pass and document
this failure as a known bug.
|
|
Date |
User |
Action |
Args |
2004-10-16 13:15:54 | a1s | create | |
|