[issue3607] test_multiprocessing failure (Unserializable message)

Jesse Noller <[EMAIL PROTECTED]> added the comment: Closing as dupe to issue3125 -- resolution: -> duplicate status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3607] test_multiprocessing failure (Unserializable message)

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: It seems that issue3125 follows the same problem; one of them could be closed IMO. Lowering priority as well. -- priority: release blocker -> high ___ Python tracker <[EMAIL PROTECTED]>

[issue3607] test_multiprocessing failure (Unserializable message)

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- priority: critical -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3607] test_multiprocessing failure (Unserializable message)

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Sorry, I did not notice the failure because test_multiprocessing have other problems on Windows. r65905 restores part of the copy_reg calls, just enough to let the tests pass. I am working on the proper fix, which is to use the custom p

[issue3607] test_multiprocessing failure (Unserializable message)

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Here's a buildbot example: http://python.org/dev/buildbot/stable/amd64%20gentoo%203.0/builds/980/step-test/0 -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]>

[issue3607] test_multiprocessing failure (Unserializable message)

New submission from Antoine Pitrou <[EMAIL PROTECTED]>: I have the following deterministic failure on py3k: test test_multiprocessing failed -- Traceback (most recent call last): File "/home/antoine/py3k/__svn__/Lib/test/test_multiprocessing.py", line 932, in test_dict self.assertEqual(sor