Tweaked the multi-processing test to run in it's own layer, to reduce

chance of affecting other tests, at least when run in a separate
process via the -j runner option.

src/ZEO/tests/testZEO.py

@@ -1268,9 +1268,15 @@ if sys.version_info >= (2, 6):
 
     class MultiprocessingTests(unittest.TestCase):
 
+        layer = ZODB.tests.util.MininalTestLayer('work_with_multiprocessing')
+
         def test_work_with_multiprocessing(self):
             "Client storage should work with multi-processing."
 
+            # Gaaa, zope.testing.runner.FakeInputContinueGenerator has no close
+            if not hasattr(sys.stdin, 'close'):
+                sys.stdin.close = lambda : None
+
             self.globs = {}
             forker.setUp(self)
             addr, adminaddr = self.globs['start_server']()
@@ -1364,7 +1370,6 @@ def test_suite():
     # unit test layer
     zeo = unittest.TestSuite()
     zeo.addTest(unittest.makeSuite(ZODB.tests.util.AAAA_Test_Runner_Hack))
-    zeo.addTest(unittest.makeSuite(MultiprocessingTests))
     zeo.addTest(doctest.DocTestSuite(
         setUp=forker.setUp, tearDown=zope.testing.setupstack.tearDown))
     zeo.addTest(doctest.DocTestSuite(ZEO.tests.IterationTests,
@@ -1388,6 +1393,8 @@ def test_suite():
     zeo.layer = ZODB.tests.util.MininalTestLayer('testZeo-misc')
     suite.addTest(zeo)
 
+    suite.addTest(unittest.makeSuite(MultiprocessingTests))
+
     # Put the heavyweights in their own layers
     for klass in slow_test_classes:
         sub = unittest.makeSuite(klass, "check")