Commit 5bb7199b authored by Tim Peters's avatar Tim Peters

The next iteration of ZODB 3.3 doesn't implicitly begin a new

transaction when a commit() fails.  One test here provoked a
failing commit(), which caused a later test to fail.  Repaired
by simply abort()'ing the failed transaction.
parent 9105193d
...@@ -85,6 +85,10 @@ RuntimeError: commit ...@@ -85,6 +85,10 @@ RuntimeError: commit
1 1
>>> len(cn.aborted) >>> len(cn.aborted)
3 3
Clean up:
>>> transaction.abort()
""" """
import transaction import transaction
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment