Guido van Rossum added the comment:
I revived my ancient PowerBook G4 just to get to the bottom of this.
The long and short of the issue seems to be that when subprocess.Popen() closes
the *read* end of the stdin pipe, fstat() on the *write* end starts failing
with EBADF. The exact line where
Guido van Rossum added the comment:
If the buildbot is still green, can you close this? I don't think it's worth
trying to formulate and test a more precise theory about the root cause, given
that it's most likely a platform bug anyway.
--
___
Ned Deily added the comment:
I agree. And there appear to have been no test_asyncio failures on the buildbot
since the checkins - closing.
--
resolution: - fixed
stage: - committed/rejected
status: open - closed
___
Python tracker
Guido van Rossum added the comment:
I find it pretty suspicious that when this fails it is always connecting the
stdin pipe. That code is also suspect in the AIX failure (issue 19293),
although for a different reason.
The only theory I have at this point is that perhaps there's a platform bug
Guido van Rossum added the comment:
I committed a patch that should hopefully fix issue 19293 -- maybe it will also
reduce the flakiness of test_subprocess_shell() on OS X?
--
___
Python tracker rep...@bugs.python.org
Ned Deily added the comment:
Success! (I think.) On my elderly 10.4 machine, as of f33cc4a175a4:
tag: tip
user:Guido van Rossum gu...@dropbox.com
date:Mon Oct 21 20:57:25 2013 -0700
files: Lib/test/test_asyncio/test_events.py
description:
Unsilence several asyncio
New submission from Ned Deily:
Since asyncio was checked in, there have been a couple of similar buildbot
failures on the OS X 10.4 (Tiger) buildbot sandwiched around a successful run.
I also saw a similar failure on a 10.4 system I have. So far, the OS X 10.6
(Snow Leopard) buildbot has
Guido van Rossum added the comment:
Thanks for reporting these. These tests sometimes pass and sometimes fail,
right? I suspect that there's a race condition in the test and slower
machines provoke it more often. I'm not sure what to do -- I won't have
time to properly debug this until after the
