[issue13063] test_concurrent_futures failures on Windows: IOError('[Errno 232] The pipe is being closed') on _send_bytes()
STINNER Victor victor.stin...@haypocalc.com added the comment: The issue has been fixed by the merge of the PEP 3151: I now get a BrokenPipeError with errno=32 and winerror=232. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13063] test_concurrent_futures failures on Windows: IOError('[Errno 232] The pipe is being closed') on _send_bytes()
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset d8d8374ddbcc by Antoine Pitrou in branch '3.2': Issue #13063: the Windows error ERROR_NO_DATA (numbered 232 and described http://hg.python.org/cpython/rev/d8d8374ddbcc New changeset 3784b6000640 by Antoine Pitrou in branch 'default': Issue #13063: the Windows error ERROR_NO_DATA (numbered 232 and described http://hg.python.org/cpython/rev/3784b6000640 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13063] test_concurrent_futures failures on Windows: IOError('[Errno 232] The pipe is being closed') on _send_bytes()
Antoine Pitrou pit...@free.fr added the comment: Hopefully this will fix the random failures (EPIPE is caught somewhere down in multiprocessing.Queue._feed). -- resolution: - fixed stage: patch review - committed/rejected status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13063] test_concurrent_futures failures on Windows: IOError('[Errno 232] The pipe is being closed') on _send_bytes()
Antoine Pitrou pit...@free.fr added the comment: Mmh, for some reason it seems it was not enough: http://www.python.org/dev/buildbot/all/builders/x86%20XP-4%203.x/builds/5328/steps/test/logs/stdio -- status: pending - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13063] test_concurrent_futures failures on Windows: IOError('[Errno 232] The pipe is being closed') on _send_bytes()
Antoine Pitrou pit...@free.fr added the comment: Ah, this is because IOError is raised because of WindowsError, thus there's no errno translation. Ok, I'd like to wait for PEP 3151 to be merged, then, because it should solve this. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13063] test_concurrent_futures failures on Windows: IOError('[Errno 232] The pipe is being closed') on _send_bytes()
Antoine Pitrou pit...@free.fr added the comment: I think the solution would be to map ERROR_NO_DATA (232 - The pipe is being closed) to EPIPE. Attached patch. -- keywords: +patch Added file: http://bugs.python.org/file23309/error_no_data.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13063] test_concurrent_futures failures on Windows: IOError('[Errno 232] The pipe is being closed') on _send_bytes()
Changes by Antoine Pitrou pit...@free.fr: -- components: +Tests nosy: +amaury.forgeotdarc stage: - patch review type: - behavior versions: +Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13063] test_concurrent_futures failures on Windows: IOError('[Errno 232] The pipe is being closed') on _send_bytes()
STINNER Victor victor.stin...@haypocalc.com added the comment: Attached patch. Could you please explain your change in generrmap.c in a comment? For example, just add a reference to this issue. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13063] test_concurrent_futures failures on Windows: IOError('[Errno 232] The pipe is being closed') on _send_bytes()
STINNER Victor victor.stin...@haypocalc.com added the comment: See also issue #13059. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13063] test_concurrent_futures failures on Windows: IOError('[Errno 232] The pipe is being closed') on _send_bytes()
New submission from STINNER Victor victor.stin...@haypocalc.com: Re-running test 'test_concurrent_futures' in verbose mode test_killed_child (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 5.79s ok test_map (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 3.63s ok test_map_exception (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 4.05s ok test_map_timeout (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 9.64s ok test_shutdown_race_issue12456 (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 3.60s ok test_submit (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 3.63s ok test_submit_keyword (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 4.09s ok test_map (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 0.13s ok test_map_exception (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 0.12s ok test_map_submits_without_iteration (test.test_concurrent_futures.ThreadPoolExecutorTest) Tests verifying issue 11777. ... 0.14s ok test_map_timeout (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 6.11s ok test_shutdown_race_issue12456 (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 0.11s ok test_submit (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 0.11s ok test_submit_keyword (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 0.11s ok test_all_completed (test.test_concurrent_futures.ProcessPoolWaitTests) ... 3.74s ok test_first_completed (test.test_concurrent_futures.ProcessPoolWaitTests) ... 5.18s ok test_first_completed_some_already_completed (test.test_concurrent_futures.ProcessPoolWaitTests) ... 5.02s ok test_first_exception (test.test_concurrent_futures.ProcessPoolWaitTests) ... 6.57s ok test_first_exception_one_already_failed (test.test_concurrent_futures.ProcessPoolWaitTests) ... 6.37s ok test_first_exception_some_already_complete (test.test_concurrent_futures.ProcessPoolWaitTests) ... 5.15s ok test_timeout (test.test_concurrent_futures.ProcessPoolWaitTests) ... 10.94s ok test_all_completed (test.test_concurrent_futures.ThreadPoolWaitTests) ... 0.12s ok test_first_completed (test.test_concurrent_futures.ThreadPoolWaitTests) ... 1.62s ok test_first_completed_some_already_completed (test.test_concurrent_futures.ThreadPoolWaitTests) ... 1.61s ok test_first_exception (test.test_concurrent_futures.ThreadPoolWaitTests) ... 3.12s ok test_first_exception_one_already_failed (test.test_concurrent_futures.ThreadPoolWaitTests) ... 2.10s ok test_first_exception_some_already_complete (test.test_concurrent_futures.ThreadPoolWaitTests) ... 1.60s ok test_timeout (test.test_concurrent_futures.ThreadPoolWaitTests) ... 6.12s ok test_no_timeout (test.test_concurrent_futures.ProcessPoolAsCompletedTests) ... 3.62s ok test_zero_timeout (test.test_concurrent_futures.ProcessPoolAsCompletedTests) ... 5.65s ok test_no_timeout (test.test_concurrent_futures.ThreadPoolAsCompletedTests) ... 0.12s ok test_zero_timeout (test.test_concurrent_futures.ThreadPoolAsCompletedTests) ... 2.11s ok test_cancel (test.test_concurrent_futures.FutureTests) ... ok test_cancelled (test.test_concurrent_futures.FutureTests) ... ok test_done (test.test_concurrent_futures.FutureTests) ... ok test_done_callback_already_cancelled (test.test_concurrent_futures.FutureTests) ... ok test_done_callback_already_failed (test.test_concurrent_futures.FutureTests) ... ok test_done_callback_already_successful (test.test_concurrent_futures.FutureTests) ... ok test_done_callback_raises (test.test_concurrent_futures.FutureTests) ... ok test_done_callback_with_cancel (test.test_concurrent_futures.FutureTests) ... ok test_done_callback_with_exception (test.test_concurrent_futures.FutureTests) ... ok test_done_callback_with_result (test.test_concurrent_futures.FutureTests) ... ok test_exception_with_success (test.test_concurrent_futures.FutureTests) ... ok test_exception_with_timeout (test.test_concurrent_futures.FutureTests) ... ok test_repr (test.test_concurrent_futures.FutureTests) ... ok test_result_with_cancel (test.test_concurrent_futures.FutureTests) ... ok test_result_with_success (test.test_concurrent_futures.FutureTests) ... ok test_result_with_timeout (test.test_concurrent_futures.FutureTests) ... ok test_running (test.test_concurrent_futures.FutureTests) ... ok test_context_manager_shutdown (test.test_concurrent_futures.ProcessPoolShutdownTest) ... 3.58s ok test_del_shutdown (test.test_concurrent_futures.ProcessPoolShutdownTest) ... 3.92s ok test_interpreter_shutdown (test.test_concurrent_futures.ProcessPoolShutdownTest) ... 5.60s FAIL test_processes_terminate (test.test_concurrent_futures.ProcessPoolShutdownTest) ... 3.67s ok test_run_after_shutdown (test.test_concurrent_futures.ProcessPoolShutdownTest) ... 0.01s ok test_context_manager_shutdown (test.test_concurrent_futures.ThreadPoolShutdownTest) ... 0.02s ok test_del_shutdown (test.test_concurrent_futures.ThreadPoolShutdownTest) ... 0.03s ok
