This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients jcea, r.david.murray
Date 2009-07-11.16:32:10
SpamBayes Score 6.560231e-09
Marked as misclassified No
Message-id <1247329933.16.0.47150397.issue6462@psf.upfronthosting.co.za>
In-reply-to
Content
The buildbots periodically report failures in the bsddb3 test suite. 
These are not reproducible and presumably are timing-based.  It would be
best if the tests could be made to pass consistently, to make the
buildbot output more useful.

Here is one such failure that I see on a semi-regular basis on trunk
(this happens in my own tests runs as well, also not consistently):

test_bsddb3
Berkeley DB 4.7.25: (June 30, 2009)
Test path prefix:  /tmp/z-test_bsddb3-11362
test test_bsddb3 failed -- Traceback (most recent call last):
  File "/home/rdmurray/python/trunk/Lib/bsddb/test/test_replication.py",
line 134, in test01_basic_replication
    self.assertTrue(time.time()<timeout)
AssertionError: False is not True

I will add others here as I capture examples.
History
Date User Action Args
2009-07-11 16:32:13r.david.murraysetrecipients: + r.david.murray, jcea
2009-07-11 16:32:13r.david.murraysetmessageid: <1247329933.16.0.47150397.issue6462@psf.upfronthosting.co.za>
2009-07-11 16:32:11r.david.murraylinkissue6462 messages
2009-07-11 16:32:10r.david.murraycreate