[ZODB-Dev] [ zodb-Bugs-536408 ] TransactionTests fail occasionally

[noreply@sourceforge.net]

Bugs item #536408, was opened at 2002-03-28 18:57
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=115628&aid=536408&group_id=15628

Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Jeremy Hylton (jhylton)
Assigned to: Nobody/Anonymous (nobody)
Summary: TransactionTests fail occasionally

Initial Comment:
This fails in the new tests that Kapil added for
unusual behavior during TPC.  There's a post in the
zodb-dev archives where he provides more details on
what may be going wrong.

FAIL: testExceptionInSubAbortSub
(ZODB.tests.testTransaction.TransactionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File
"lib.linux-i686-2.1/ZODB/tests/testTransaction.py",
line 494, in testExceptionInSubAbortSub
    assert self.sub3._p_jar.cabort_sub == 1
AssertionError

2002-03-28T13:45:30 ERROR(200) ZODB A storage error
occured during object abort This shouldn't happen. 
Traceback (innermost last):
  File lib.linux-i686-2.1/ZODB/Transaction.py, line
306, in commit
  File
lib.linux-i686-2.1/ZODB/tests/testTransaction.py, line
635, in tpc_abort
  File
lib.linux-i686-2.1/ZODB/tests/testTransaction.py, line
614, in check
TestTxnException:  error tpc_abort



------
2002-03-28T13:45:30 PANIC(300) ZODB A storage error
occurred in the last phase of a two-phase commit.  This
shouldn't happen. The application may be in a hosed
state, so transactions will not be allowed to commit
until the site/storage is reset by a restart. 
Traceback (innermost last):
  File lib.linux-i686-2.1/ZODB/Transaction.py, line
273, in commit
  File
lib.linux-i686-2.1/ZODB/tests/testTransaction.py, line
639, in tpc_finish
  File
lib.linux-i686-2.1/ZODB/tests/testTransaction.py, line
614, in check
TestTxnException:  error tpc_finish



------
2002-03-28T13:45:30 PANIC(300) ZODB A storage error
occurred in the last phase of a two-phase commit.  This
shouldn't happen. The application may be in a hosed
state, so transactions will not be allowed to commit
until the site/storage is reset by a restart. 
Traceback (innermost last):
  File lib.linux-i686-2.1/ZODB/Transaction.py, line
273, in commit
  File
lib.linux-i686-2.1/ZODB/tests/testTransaction.py, line
639, in tpc_finish
  File
lib.linux-i686-2.1/ZODB/tests/testTransaction.py, line
614, in check
TestTxnException:  error tpc_finish



------
2002-03-28T13:45:30 BLATHER(-100) ZODB Commiting
subtransaction of size 14348


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=115628&aid=536408&group_id=15628