[Python-Dev] [Python-checkins] Python Regression Test Failures all (1)
Tim Peters
tim.peters at gmail.com
Fri Mar 31 18:47:59 CEST 2006
[Neal Norwitz]
"""
test_bsddb3
Exception in thread reader 4:
Traceback (most recent call last):
File "/home/neal/python/trunk/Lib/threading.py", line 473, in __bootstrap
self.run()
File "/home/neal/python/trunk/Lib/threading.py", line 453, in run
self.__target(*self.__args, **self.__kwargs)
File "/home/neal/python/trunk/Lib/bsddb/test/test_thread.py", line
275, in readerThread
rec = dbutils.DeadlockWrap(c.next, max_retries=10)
File "/home/neal/python/trunk/Lib/bsddb/dbutils.py", line 62, in DeadlockWrap
return function(*_args, **_kwargs)
DBLockDeadlockError: (-30996, 'DB_LOCK_DEADLOCK: Locker killed to
resolve a deadlock')
Exception in thread writer 0:
Traceback (most recent call last):
File "/home/neal/python/trunk/Lib/threading.py", line 473, in __bootstrap
self.run()
File "/home/neal/python/trunk/Lib/threading.py", line 453, in run
self.__target(*self.__args, **self.__kwargs)
File "/home/neal/python/trunk/Lib/bsddb/test/test_thread.py", line
254, in writerThread
self.assertEqual(data, self.makeData(key))
File "/home/neal/python/trunk/Lib/unittest.py", line 334, in failUnlessEqual
(msg or '%r != %r' % (first, second))
AssertionError: None != '0003-0003-0003-0003-0003'
[and so on]
"""
[Jeremy Hylton]
> I haven't run regrtest.py -u all in a while. Are these sorts of
> errors just tolerated?
test_bsddb3 has always failed in these ways, and I believe on all
platforms, although on my WinXP box it only happens if my box is
heavily loaded with other stuff. Normally a DBLockDeadlockError
doesn't even cause the test to fail, presumably because the exception
occurs in a thread unittest doesn't know about (you'll recall the
convolutions we endured to get unittest to notice errors in ZODB/ZEO
test threads).
For example, here's a recent buildbot run where test_bsddb3 passed
despite a DBLockDeadlockError:
http://www.python.org/dev/buildbot/all/x86%20gentoo%20trunk/builds/223/step-test/0
The prospects for fixing it appear dim; PCbuild/readme.txt has noted
for years "I'm told that DBLockDeadlockError is expected at times".
More information about the Python-Dev
mailing list