[Python-Dev] [Python-checkins] Python Regression Test Failures all (1)

[Jeremy Hylton]

On 3/1/06, Neal Norwitz <neal at metaslash.com> wrote:
> 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'
>
> Exception in thread writer 1:
> 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 != '1000-1000-1000-1000-1000'

I haven't run regrtest.py -u all in a while.  Are these sorts of
errors just tolerated?

Jeremy