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.

Title: bsddb3 intermittent test failures
Type: behavior Stage: resolved
Components: Tests Versions: Python 2.7, Python 2.6
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: jcea Nosy List: jcea, r.david.murray, vstinner
Priority: normal Keywords: buildbot

Created on 2009-07-11 16:32 by r.david.murray, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (8)
msg90426 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2009-07-11 16:32
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):

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/",
line 134, in test01_basic_replication
AssertionError: False is not True

I will add others here as I capture examples.
msg90732 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2009-07-20 14:47
Another buildbot intermittent failure, this one from

ie: the x86 XP-4 buildbot:

Traceback (most recent call last):
line 524, in __bootstrap_inner
line 477, in run
    self.__target(*self.__args, **self.__kwargs)
line 306, in readerThread
    rec = dbutils.DeadlockWrap(, max_retries=10)
line 68, in DeadlockWrap
    return function(*_args, **_kwargs)
DBLockDeadlockError: (-30994, 'DB_LOCK_DEADLOCK: Locker killed to
resolve a deadlock')

That run also shows the replication timeout error, which that buildbot
often produces.
msg94861 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2009-11-03 14:16
Unless someone objects, I'm going to disable the replication timeout
check unconditionally, since it is the worst culprit for buildbot
stability on 2.x.  Note that issue 3892 indicates it happens
consistently on windows, and there was already a partial disable for
that platform.  All the other tests usually succeed even if that
particular assert fails.
msg94915 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2009-11-05 01:54
I was able to consistently reproduce the timeout on my Gentoo buildbot
running in a vserver virthost.  After some experimentation and perusing
the related issue 3892, I discovered that by increasing the timeout I
could get the test to consistently pass in my buildbot.  However, it
does occasionally produce the DB_LOCK_DEADLOCK traceback in one of the
threads. (Two times out of about 17 runs in a loop).

I've checked an increase in the timeout for the two replication tests
into trunk in r76116.  In some of my experiments it was clear that the
base replication case is much quicker than the ReplicationManager case,
so I made the ReplicationManager timeout longer.  I'm hoping this will
fix the line 315 failure in the windows buildbot, since it does
sometimes pass.
msg94959 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2009-11-06 02:40
The deadlock error is still there, so I'm leaving this open, but it is
no longer causing buildbot instability.
msg104188 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2010-04-26 00:04
Is the following error related to this issue? Windows7 2.6/builds/256/steps/test/logs/stdio

test test_bsddb3 failed -- Traceback (most recent call last):
  File "D:\cygwin\home\db3l\buildarea\2.6.bolen-windows7\build\lib\bsddb\test\", line 127, in test03_lock_timeout
    self.assertTrue((end_time-start_time) >= 0.0999)
msg221129 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2014-06-20 22:50
@David this is now out of date?
msg354726 - (view) Author: Jesús Cea Avión (jcea) * (Python committer) Date: 2019-10-15 13:17
Time to die.
Date User Action Args
2022-04-11 14:56:50adminsetgithub: 50711
2019-10-15 13:17:58jceasetstatus: open -> closed
resolution: wont fix
messages: + msg354726

stage: needs patch -> resolved
2019-03-15 23:36:34BreamoreBoysetnosy: - BreamoreBoy
2014-06-20 22:50:42BreamoreBoysetnosy: + BreamoreBoy
messages: + msg221129
2010-08-22 20:28:06floxsetkeywords: + buildbot
2010-04-26 00:04:33vstinnersetnosy: + vstinner
messages: + msg104188
2009-11-06 02:41:08r.david.murraysetkeywords: - buildbot
2009-11-06 02:40:21r.david.murraysetmessages: + msg94959
2009-11-05 01:54:03r.david.murraysetmessages: + msg94915
2009-11-03 14:16:21r.david.murraysetmessages: + msg94861
versions: + Python 2.6
2009-10-30 19:46:37r.david.murraysetkeywords: + buildbot
2009-07-20 14:47:32r.david.murraysetmessages: + msg90732
2009-07-11 16:32:11r.david.murraycreate