Mark Lawrence added the comment:
Is any follow up needed to this or can it be closed as bsddb has been removed
from Python 3?
--
nosy: +BreamoreBoy
versions: -Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3892
R. David Murray added the comment:
Yeah, let's just close it. Nobody is likely to care enough to try to fix it
properly.
--
resolution: - out of date
stage: needs patch - committed/rejected
status: languishing - closed
___
Python tracker
R. David Murray rdmur...@bitdance.com added the comment:
Applied skip patch to trunk in r78558, and 2.6 in 78560.
--
status: open - languishing
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3892
Gregory P. Smith g...@krypto.org added the comment:
r.david.murray - sounds like a good idea.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3892
___
Changes by R. David Murray rdmur...@bitdance.com:
--
keywords: +buildbot -patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3892
___
___
R. David Murray rdmur...@bitdance.com added the comment:
Hmm. That's not actually the same timeout. What that means is that if the
startup timeout triggers, then a subsequent test (one that is looking for the
results of a client transaction) fails, which contradicts the earlier
observation
R. David Murray rdmur...@bitdance.com added the comment:
Since this isn't likely to get fixed and it is causing buildbot instability, I
propose the attached patch to just skip the remainder of the test method if
this second timeout happens.
--
keywords: +patch
Added file:
Florent Xicluna la...@yahoo.fr added the comment:
Still occurs, on 2010-01-13.
http://www.python.org/dev/buildbot/all/builders/x86%20Ubuntu%20trunk/builds/264
--
nosy: +flox
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3892
R. David Murray rdmur...@bitdance.com added the comment:
Failures still occur occasionally even with the timeout set to 60. So
I've turned the check that is skipped on Windows from an assertion into
a warning only on all other platforms, since bsddb support isn't
actively maintained and is gone
