[ZODB-Dev] checkModifyAfterAbortVersion fails

[Mark McEahern]

I was inspired by Magnus Heino's reporting that he had no problems on Red
Hat 7.3, so I:

1.  Installed RH 7.3 fresh.
2.  Installed Python 2.1.3:

    ./configure
    make
    sudo make altinstall

3.  Installed Zope 2.5.1 (from full source tarball off of zope.org).
4.  Got ZEO from CVS (a simple 'cvs co ZEO' gets HEAD --true?).

I do:

  export PYTHONPATH='/usr/local/Zope/lib/python'
  cd ZEO
  python2.1 setup.py build
  python2.1 test.py -v -v

and it breezes through (i.e., passes) the tests that sometimes hung before
(checkCommitLock2OnAbort and checkCommitLock2OnCommit), however it fails
checkModifyAfterAbortVersion:

======================================================================
ERROR: checkModifyAfterAbortVersion (ZEO.tests.testZEO.ZEOFileStorageTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/local/Zope/lib/python/ZODB/tests/VersionStorage.py", line 221,
in checkModifyAfterAbortVersion
    revid = self._dostore(oid, revid=revid, data=MinPO(52))
  File "/usr/local/Zope/lib/python/ZODB/tests/StorageTestBase.py", line 161,
in _dostore
    r2 = self._storage.tpc_vote(t)
  File "lib/ZEO/ClientStorage.py", line 328, in tpc_vote
    return self._check_serials()
  File "lib/ZEO/ClientStorage.py", line 314, in _check_serials
    raise s
ConflictError: database conflict error (oid 0000000000000001, serial was
03474d79419b7155, now 03474d7940d67f88)

----------------------------------------------------------------------
Ran 103 tests in 70.047s

FAILED (errors=1)

// mark

-