[issue23713] intermittent failure of multiprocessing unit test test_imap_unordered_handle_iterable_exception

Roundup Robot added the comment: New changeset 0ac30526c208 by Serhiy Storchaka in branch '2.7': Issue #23713: Fixed fragility of test_imap_unordered_handle_iterable_exception. https://hg.python.org/cpython/rev/0ac30526c208 New changeset 0eb5968c15ad by Serhiy Storchaka in branch '3.4': Issue #2

[issue23713] intermittent failure of multiprocessing unit test test_imap_unordered_handle_iterable_exception

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: commit review -> resolved status: open -> closed ___ Python tracker ___

[issue23713] intermittent failure of multiprocessing unit test test_imap_unordered_handle_iterable_exception

Serhiy Storchaka added the comment: Thanks for your explanation and sorry for the delay Davin. Yes, it makes sense. -- assignee: davin -> serhiy.storchaka stage: patch review -> commit review ___ Python tracker ___

[issue23713] intermittent failure of multiprocessing unit test test_imap_unordered_handle_iterable_exception

Davin Potts added the comment: Serhiy: If my comments on your questions make sense, should we go ahead with the patch as it is? -- ___ Python tracker ___ __

[issue23713] intermittent failure of multiprocessing unit test test_imap_unordered_handle_iterable_exception

Berker Peksag added the comment: Just saw this on x86 Tiger 3.x: == FAIL: test_imap_unordered_handle_iterable_exception (test.test_multiprocessing_fork.WithProcessesTestPool)

[issue23713] intermittent failure of multiprocessing unit test test_imap_unordered_handle_iterable_exception

Davin Potts added the comment: Serhiy: If I understand correctly what you suggest, calling sorted(it) or list(it) would run the iterator all the way until it raises the SayWhenError exception, triggering the self.assertRaises before it ever actually gets to call the self.assertEqual or self.as

[issue23713] intermittent failure of multiprocessing unit test test_imap_unordered_handle_iterable_exception

Serhiy Storchaka added the comment: Why not use just self.assertEqual(sorted(it), list(map(sqr, list(range(10) or self.assertCountEqual(list(it), list(map(sqr, list(range(10) ? -- nosy: +serhiy.storchaka ___ Python tracker

[issue23713] intermittent failure of multiprocessing unit test test_imap_unordered_handle_iterable_exception

Davin Potts added the comment: Attaching patch for this fragile test for 2.7 branch. Patches have been put through test.regrtest on OS X 10.10 (64-bit), FreeBSD 10.1 i386 (32-bit), and Raspbian Debian (ARMv6) thus far. -- stage: -> patch review Added file: http://bugs.python.org/file

[issue23713] intermittent failure of multiprocessing unit test test_imap_unordered_handle_iterable_exception

Davin Potts added the comment: Attaching patch for this fragile test for default/3.5 and 3.4 branches. Blame for implementing the fragile test falls to @davin. In my own defense, @davin also discovered it in testing on FreeBSD 10.1 i386-RELEASE. -- keywords: +patch Added file: http:/

[issue23713] intermittent failure of multiprocessing unit test test_imap_unordered_handle_iterable_exception

New submission from Davin Potts: test_imap_unordered_handle_iterable_exception fails intermittently on some platforms due to the test being too rigid (fragile) about the order of the items being iterated over which, as the name would imply, is not guaranteed. Of the multiprocessing module's te