1. 14 Jun, 2005 1 commit
  2. 09 Jun, 2005 2 commits
  3. 06 Jun, 2005 4 commits
  4. 03 Jun, 2005 2 commits
  5. 02 Jun, 2005 4 commits
  6. 31 May, 2005 2 commits
  7. 27 May, 2005 3 commits
  8. 26 May, 2005 2 commits
  9. 20 May, 2005 3 commits
  10. 19 May, 2005 5 commits
  11. 18 May, 2005 1 commit
  12. 13 May, 2005 1 commit
  13. 12 May, 2005 3 commits
    • Tim Peters's avatar
      checkUndoInVersion(): Add an optional `hook` argument. · b8bcad99
      Tim Peters authored
      This gets called "in the middle" of the test, if specified.
      ZRS 1.5 uses this to pass a callback that arranges to start a
      ZRS secondary then.  ZRS had its own copy of this test, but
      it's a miserable & messy test, and the copy it had failed in
      5 different places when using ZODB 3.4 (it had gotten way of
      synch with changes since ZODB 3.2).
      
      Also removed all traces of the bizarre _x_dostore() method.
      Not sure what that was about, but if the comments were right
      we don't care about ZEO 1.0 anymore.
      b8bcad99
    • Tim Peters's avatar
      ZEO/tests/zeoserver.py, log(): repair broken interface · 6a7a79dc
      Tim Peters authored
      between old logging code and the use of Python's logging
      package.
      
      ZODB/tests/TransactionalUndoStorage.py, _exercise_info_indices():
      Jeez Louise, the new tests I added for undoInfo+undoLog work fine
      in ZODB, but break the ZRS tests(!).  They close the DB "too soon",
      and in one of the ZRS scenarios that leaves a recovering secondary
      without a primary to recover from.
      6a7a79dc
    • Tim Peters's avatar
      undoInfo() and undoLog() almost always returned wrong # of results. · 38aa0758
      Tim Peters authored
      Repaired, + new tests.
      38aa0758
  14. 11 May, 2005 3 commits
  15. 09 May, 2005 2 commits
  16. 06 May, 2005 2 commits