Berkeley test errors in 2.3.4c1
I tried 2.3.4rc1 on Win XP SP1, and got 30 errors in test_bsddb3. Opened a bug report: http://www.python.org/sf/954530 How's test_bsddb3 working on other 2.3.4c1 installations (I encourage adding info to the bug report instead of via email)?
On Sat, May 15, 2004 at 02:06:37PM -0400, Tim Peters wrote:
I tried 2.3.4rc1 on Win XP SP1, and got 30 errors in test_bsddb3. Opened a bug report:
http://www.python.org/sf/954530
How's test_bsddb3 working on other 2.3.4c1 installations (I encourage adding info to the bug report instead of via email)?
fixed. it was broken test case due to a different default behaviour on 2.3 than 2.4. sorry about that. i took the easy route and just cauterized the broken test rather than writing a proper one for the 2.3 branch.
[Gregory P. Smith, on http://www.python.org/sf/954530 ]
fixed. it was broken test case due to a different default behaviour on 2.3 than 2.4. sorry about that. i took the easy route and just cauterized the broken test rather than writing a proper one for the 2.3 branch.
Thanks! I ran the original on WinXP from the released 2.3.4c1, but am not able to build my own 2.3 Python on that box (well, not without more setup time than I can give to it now). Going back to a Win98SE box and building from current release23-maint CVS, test_bsddb3 failed with 4 instances of a different error (see attached). But, IIRC, the test has always failed on Win98SE in this way. All the errors I reported above went away.
On Sat, May 15, 2004 at 08:25:01PM -0400, Tim Peters wrote:
[Gregory P. Smith, on http://www.python.org/sf/954530 ]
fixed. it was broken test case due to a different default behaviour on 2.3 than 2.4. sorry about that. i took the easy route and just cauterized the broken test rather than writing a proper one for the 2.3 branch.
Thanks! I ran the original on WinXP from the released 2.3.4c1, but am not able to build my own 2.3 Python on that box (well, not without more setup time than I can give to it now). Going back to a Win98SE box and building from current release23-maint CVS, test_bsddb3 failed with 4 instances of a different error (see attached). But, IIRC, the test has always failed on Win98SE in this way. All the errors I reported above went away.
====================================================================== ERROR: test01_basics (bsddb.test.test_dbshelve.EnvBTreeShelveTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "C:\CODE\23\lib\bsddb\test\test_dbshelve.py", line 75, in test01_basics self.do_open() File "C:\CODE\23\lib\bsddb\test\test_dbshelve.py", line 238, in do_open self.env.open(homeDir, self.envflags | db.DB_INIT_MPOOL | db.DB_CREATE) DBAgainError: (11, 'Resource temporarily unavailable -- unable to join the environment')
Yeah I'd chalk that one up to Win98. -g
[Gregory P. Smith, on test_bsddb3 Win98SE failures in test01_basics]
Yeah I'd chalk that one up to Win98.
Me too <wink>. Back over on WinXP and *current* (HEAD) CVS, there's one failure, which I believe is real: ERROR: test04_n_flag (bsddb.test.test_compat.CompatibilityTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "C:\Code\python\lib\bsddb\test\test_compat.py", line 86, in test04_n_flag f = hashopen(self.filename, 'n') File "C:\Code\python\lib\bsddb\__init__.py", line 293, in hashopen d.open(file, db.DB_HASH, flags, mode) DBInvalidArgError: (22, 'Invalid argument -- DB_TRUNCATE illegal with locking specified') I suspect Sleepycat screwed us there, changing the rules in midstream. Someone on c.l.py appeared to track down the same thing here, but in an app instead of in our test suite: http://mail.python.org/pipermail/python-list/2004-May/220168.html The change log of Berkeley DB 4.2.52 says "9. Fix a bug to now disallow DB_TRUNCATE on opens in locking environments, since we cannot prevent race conditions ..."
participants (2)
-
Gregory P. Smith -
Tim Peters