[issue10737] test_concurrent_futures failure on Windows

Brian Quinlan added the comment: Fixed in r87673. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-b

[issue10737] test_concurrent_futures failure on Windows

Brian Quinlan added the comment: I'm good, thanks Brian C. It looks like SetEvent is failing with ERROR_INVALID_HANDLE. CRITICAL:root:SetEvent(2044) failed with 0, GetLastError() = 6 CRITICAL:root:SetEvent(2064) failed with 0, GetLastError() = 6 CRITICAL:root:SetEvent(2220) failed with 0, Get

[issue10737] test_concurrent_futures failure on Windows

Brian Curtin added the comment: You can create a branch, checkin to that branch, then specify that a specific buildbot runs your branch. See the "force build" page of a build slave. Additionally, I can give you access to my build slave, the Windows Server 2008 one, but that may take a few day

[issue10737] test_concurrent_futures failure on Windows

Brian Quinlan added the comment: What's the best way for me to test this? The problem occurs on a Windows-only code path but there is not enough information for me to debug it. Should I check-in some additional diagnostics, wait for the buildbot to run, collect my data and then rollback my ch

[issue10737] test_concurrent_futures failure on Windows

Changes by Antoine Pitrou : -- nosy: +brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue10737] test_concurrent_futures failure on Windows

Changes by Georg Brandl : -- priority: high -> deferred blocker ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10737] test_concurrent_futures failure on Windows

New submission from Antoine Pitrou : This has been happening recently on our Windows Server 2008 buildbot: == FAIL: test_first_completed (test.test_concurrent_futures.ThreadPoolWaitTests) ---