- 30 Apr, 2004 1 commit
-
-
Tim Peters authored
"sporadic Zope crashes" http://collector.zope.org/Zope/553 This is much like the test of the same name I just added to the Zope 2.6 and 2.7 branches, but reworded to use ZODB 3.3isms. The HEAD bucket conflict resolution code is already correct in this case, so no other code change here -- adding this test to ensure it stays correct.
-
- 29 Apr, 2004 2 commits
-
-
Fred Drake authored
-
Tim Peters authored
-
- 27 Apr, 2004 2 commits
-
-
Marius Gedminas authored
-
Marius Gedminas authored
-
- 25 Apr, 2004 2 commits
-
-
Gintautas Miliauskas authored
'test left threads behind' warnings. Tests in testZEO sometimes do that too, but that's hard to reproduce.
-
Gintautas Miliauskas authored
to zLOG other than a few comments. This definitely broke the log analyzers pretty bad.
-
- 24 Apr, 2004 2 commits
-
-
Gintautas Miliauskas authored
This probably broke the log analyzers... :(
-
Gintautas Miliauskas authored
-
- 23 Apr, 2004 4 commits
-
-
Gintautas Miliauskas authored
-
Gintautas Miliauskas authored
-
Tim Peters authored
fiddly code trying to prevent OverflowError.
-
Tim Peters authored
conversion (this is an --all test, so the original committer probably didn't run it). Introduced a trivial new module (loglevels.py) to centralize creating the custom log levels ZODB/ZEO want to use.
-
- 22 Apr, 2004 4 commits
-
-
Gintautas Miliauskas authored
processing the messages because the format might have changed a little bit.
-
Fred Drake authored
-
Fred Drake authored
(the tests themselves still aren't being run; we need decent save/restore behavior from the logging package to do this properly)
-
Fred Drake authored
logging directly
-
- 20 Apr, 2004 1 commit
-
-
Fred Drake authored
later
-
- 19 Apr, 2004 5 commits
-
-
Tim Peters authored
didn't recognize its version number. As a result, 3.3a3 went out with ZODB/__init__.py claiming it was version 3.3a2. Repaired that, but by changing what release.py looks for.
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
cause of the: TypeError: unpack() argument 2 must be string or read-only buffer, not None failure often seen in overnight testrunner reports now, coming from the checkConcurrentUpdatesInVersions test. If the hypothesis is correct, we'll see a failure of the new assert end is not None instead.
-
Barry Warsaw authored
returns a datetime.timedelta instead of a float. Added test case and documentation.
-
- 17 Apr, 2004 4 commits
-
-
Gintautas Miliauskas authored
-
Gintautas Miliauskas authored
-
Gintautas Miliauskas authored
-
Gintautas Miliauskas authored
-
- 16 Apr, 2004 13 commits
-
-
Jeremy Hylton authored
-
Tim Peters authored
-
Tim Peters authored
-
Jeremy Hylton authored
-
Tim Peters authored
-
Jeremy Hylton authored
-
Jeremy Hylton authored
-
Tim Peters authored
-
Tim Peters authored
thinks they live.
-
Jeremy Hylton authored
-
Jeremy Hylton authored
The old code used itertools.chain(), which didn't work as expected. If the first of the two iterator grew after the chain had started consuming the second iterator, the new element(s) in the first iterator would never be consumed. Fix this bug by eliminating the need for chaining. Process all the _added_during_commit objects at the end, each with its own ObjectWriter instance.
-
Jeremy Hylton authored
-
Jeremy Hylton authored
Add explanation for __getattr__ and friends.
-