[Checkins] [zopefoundation/ZEO] 7cb600: use a "threadless" multi-processing queue

[GitHub]

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

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

  Log Message:
  -----------
  use a "threadless" multi-processing queue

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.


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

  Changed paths:
    M src/ZEO/tests/ZEO4/StorageServer.py
    M src/ZEO/tests/forker.py

  Log Message:
  -----------
  Added a timeout argument to the ZEO4 server (copy)

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.


Compare: https://github.com/zopefoundation/ZEO/compare/42516476d5f1...9d765e8d2e0f