Author martin.panter
Recipients martin.panter, meador.inge, python-dev, twouters, tylercrompton
Date 2016-05-15.03:12:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1463281934.55.0.472606896592.issue26870@psf.upfronthosting.co.za>
In-reply-to
Content
My test locked up on an OS X buildbot <http://buildbot.python.org/all/builders/AMD64%20Snow%20Leop%203.x/builds/4623/steps/test/logs/stdio>:

Timeout (0:15:00)!
Thread 0x00007fff71296cc0 (most recent call first):
  File "/Users/buildbot/buildarea/3.x.murray-snowleopard/build/Lib/subprocess.py", line 1612 in _try_wait
  File "/Users/buildbot/buildarea/3.x.murray-snowleopard/build/Lib/subprocess.py", line 1662 in wait
  File "/Users/buildbot/buildarea/3.x.murray-snowleopard/build/Lib/subprocess.py", line 1003 in __exit__
  File "/Users/buildbot/buildarea/3.x.murray-snowleopard/build/Lib/test/test_readline.py", line 146 in run_pty
  File "/Users/buildbot/buildarea/3.x.murray-snowleopard/build/Lib/test/test_readline.py", line 115 in test_auto_history_disabled

The parent was hanging as it exits the child proc context manager, waiting for the child to exit. Perhaps some exception happened in the parent before it could write to the child, so the child is still waiting on input. So I added code to close the master in case of exception, which may at least help understand the situation.
History
Date User Action Args
2016-05-15 03:12:14martin.pantersetrecipients: + martin.panter, twouters, meador.inge, python-dev, tylercrompton
2016-05-15 03:12:14martin.pantersetmessageid: <1463281934.55.0.472606896592.issue26870@psf.upfronthosting.co.za>
2016-05-15 03:12:14martin.panterlinkissue26870 messages
2016-05-15 03:12:13martin.pantercreate