I wrote:
> But I can open a ticket with the proposed changes if that would help.
Figure it can't hurt - I've created issue 1112 with the proposed patch
to the test_1413192.py module.
-- David
___
Python-Dev mailing list
Python-Dev@python.org
http://ma
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
>> warning: DBTxn aborted in destructor. No prior commit() or abort().
>
> I have seen these as well. bsddb isn't very forgiving when you have
> a Python exception inside a bsddb transaction, in the test suite.
> IIRC, the exception will abort the tra
> warning: DBTxn aborted in destructor. No prior commit() or abort().
I have seen these as well. bsddb isn't very forgiving when you have
a Python exception inside a bsddb transaction, in the test suite.
IIRC, the exception will abort the transaction, then the unittest
fixture teardown will close
I previously wrote:
> (...)
> which I tracked back to an abort() call within the bsddb library as
> final destruction is happening at Python exit. (When clearing the
> test_bsddb module, and the bsddb wrapper tries to access a log file
> related to an open transaction). (...)
For those more fami
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
>> My build slave (http://www.python.org/dev/buildbot/trunk/x86%20XP%20trunk)
>> keeps failing because of a crash that appears to be in the bsddb
>> module. I assume the master deems the slave to be lost because it's
>> sitting there waiting on me to
On 9/5/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > My build slave (http://www.python.org/dev/buildbot/trunk/x86%20XP%20trunk)
> > keeps failing because of a crash that appears to be in the bsddb
> > module. I assume the master deems the slave to be lost because it's
> > sitting there wait
> My build slave (http://www.python.org/dev/buildbot/trunk/x86%20XP%20trunk)
> keeps failing because of a crash that appears to be in the bsddb
> module. I assume the master deems the slave to be lost because it's
> sitting there waiting on me to make a choice on the "debug/abort"
> dialog box.
W
