➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author sable
Recipients sable
Date 2010-09-15.16:30:32
SpamBayes Score 0.00012262822
Marked as misclassified No
Message-id <1284568234.82.0.42184878799.issue9862@psf.upfronthosting.co.za>
In-reply-to
Content 
On AIX, the test test_communicate_pipe_buf in test_subprocess will hang forever (in py3k and py27):

test_communicate_pipe_buf (__main__.ProcessTestCase) ... 


  File "Lib/test/test_subprocess.py", line 386, in test_communicate_pipe_buf
    (stdout, stderr) = p.communicate(string_to_write)
  File "/san_cis/home/cis/data/bamboo-home-agent-runtime/xml-data/build-dir/RTAIX30-SUP/Python-2.7-svn/Lib/subprocess.py", line 740, in communicate
    return self._communicate(input)
  File "/san_cis/home/cis/data/bamboo-home-agent-runtime/xml-data/build-dir/RTAIX30-SUP/Python-2.7-svn/Lib/subprocess.py", line 1257, in _communicate
    stdout, stderr = self._communicate_with_poll(input)
  File "/san_cis/home/cis/data/bamboo-home-agent-runtime/xml-data/build-dir/RTAIX30-SUP/Python-2.7-svn/Lib/subprocess.py", line 1320, in _communicate_with_poll
    input_offset += os.write(fd, chunk)
KeyboardInterrupt

The comment in this test indicates:
  # communicate() with writes larger than pipe_buf
  # This test will probably deadlock rather than fail, if
  # communicate() does not work properly.

So I guess it means communicate() does not work properly on AIX.
History
Date User Action Args
2010-09-15 16:30:34sablesetrecipients: + sable
2010-09-15 16:30:34sablesetmessageid: <1284568234.82.0.42184878799.issue9862@psf.upfronthosting.co.za>
2010-09-15 16:30:33sablelinkissue9862 messages
2010-09-15 16:30:32sablecreate