1. 05 Aug, 2016 3 commits
  2. 04 Aug, 2016 8 commits
  3. 03 Aug, 2016 4 commits
    • Jim Fulton's avatar
      Fixed a bug handling ZEO4 invalidations during cache verification · 5ba506e7
      Jim Fulton authored
      ZEO4 servers can send invalidations out of order with
      ``getInvalidations`` results, presumably because ``getInvalidations``
      didn't get the commit lock.  ZEO4 clients worked around this (maybe
      not directly) by queuing invalidations during cache verification.
      ZEO5 servers don't send invalidations out of order with
      ``getInvalidations`` calls and the ZEO5 client didn't need an
      invalidation queue, except they do need one to work correctly with
      ZEO4 servers. :/
      5ba506e7
    • Jim Fulton's avatar
      Don't print server log on error and import ZEO · c7a96bae
      Jim Fulton authored
      The later seems to be necessary when running the test multiple times
      in a test run (as I did while debugging a test failure).
      c7a96bae
    • Jim Fulton's avatar
      Added a timeout argument to the ZEO4 server (copy) · 9d765e8d
      Jim Fulton authored
      It turns out the ZEO4 server doesn't shutdown cleanly in tests without
      a shorter timeout (like the one I added for ZEO5).
      
      For now, this is just in the copy used in the ZEO5 tests.  If I have
      to updatre the copy at some point (hopefully not), then I'll add this
      to ZEO4 proper.
      9d765e8d
    • Jim Fulton's avatar
      use a "threadless" multi-processing queue · 7cb60051
      Jim Fulton authored
      To avoid spew about threads being left behind by tests.  The normal
      multi-processing.Queue uses a thread to send data and the machinery
      for stopping this thread seems to be buggy (or inscrutable) on Linux,
      causing test runner spew that made output hard to interpret.
      7cb60051
  4. 02 Aug, 2016 4 commits
  5. 30 Jul, 2016 2 commits
  6. 28 Jul, 2016 5 commits
  7. 21 Jul, 2016 9 commits
  8. 20 Jul, 2016 2 commits
  9. 19 Jul, 2016 3 commits