[Checkins] [zopefoundation/ZEO] c7a96b: Don't print server log on error and import ZEO

[GitHub]

  Branch: refs/heads/zeo4-server-support
  Home:   https://github.com/zopefoundation/ZEO
  Commit: c7a96bae0c931a4f3f760caa729317467ca963c7
      https://github.com/zopefoundation/ZEO/commit/c7a96bae0c931a4f3f760caa729317467ca963c7
  Author: Jim Fulton <jim at zope.com>
  Date:   2016-08-03 (Wed, 03 Aug 2016)

  Changed paths:
    M src/ZEO/tests/testConnection.py

  Log Message:
  -----------
  Don't print server log on error and import ZEO

The later seems to be necessary when running the test multiple times
in a test run (as I did while debugging a test failure).


  Commit: 5ba506e7f173370377feb6761b532f86e7681f4d
      https://github.com/zopefoundation/ZEO/commit/5ba506e7f173370377feb6761b532f86e7681f4d
  Author: Jim Fulton <jim at zope.com>
  Date:   2016-08-03 (Wed, 03 Aug 2016)

  Changed paths:
    M src/ZEO/asyncio/client.py

  Log Message:
  -----------
  Fixed a bug handling ZEO4 invalidations during cache verification

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. :/


Compare: https://github.com/zopefoundation/ZEO/compare/9d765e8d2e0f...5ba506e7f173