New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test_subprocess failure #55713
Comments
====================================================================== Traceback (most recent call last):
File "/home2/buildbot2/slave/3.x.loewis-parallel/build/Lib/test/test_subprocess.py", line 133, in test_check_output_timeout
self.assertEqual(c.exception.output, b'BDFL')
AssertionError: b'' != b'BDFL' ====================================================================== Traceback (most recent call last):
File "/home2/buildbot2/slave/3.x.loewis-parallel/build/Lib/test/test_subprocess.py", line 133, in test_check_output_timeout
self.assertEqual(c.exception.output, b'BDFL')
AssertionError: b'' != b'BDFL' ====================================================================== Traceback (most recent call last):
File "/home2/buildbot2/slave/3.x.loewis-parallel/build/Lib/test/test_subprocess.py", line 133, in test_check_output_timeout
self.assertEqual(c.exception.output, b'BDFL')
AssertionError: b'' != b'BDFL' |
I can't reproduce this. I've tested on: It seems reasonable to me that the interpreter should be able to |
Well, we have some very slow buildbots and others which seem quite loaded too. In my experience such a low timeout value may be enough for light in-process stuff such as lock.acquire() or select(), but if you spawn a whole new process you should let the system breathe a bit more. I know this also unfortunately increases the test runtime, but try to bump it up to at least 1.5 seconds. |
I increased the timeout in [fd2b3eac6756] and the buildbot is passing now: |
There seems to be another kind, sporadic, of failure on the same buildbot: test test_subprocess failed -- Traceback (most recent call last):
File "/home2/buildbot2/slave/3.x.loewis-parallel/build/Lib/test/test_subprocess.py", line 626, in test_wait_timeout
self.assertEqual(p.wait(timeout=2), 0)
File "/home2/buildbot2/slave/3.x.loewis-parallel/build/Lib/subprocess.py", line 1489, in wait
raise TimeoutExpired(self.args)
subprocess.TimeoutExpired: <unprintable TimeoutExpired object> |
Other failures on the Sparc debian buildbot (which is quite slow): ====================================================================== Traceback (most recent call last):
File "/home/pybot/buildarea-sid/3.x.klose-debian-sparc/build/Lib/test/test_subprocess.py", line 630, in test_wait_timeout
self.assertEqual(p.wait(timeout=2), 0)
File "/home/pybot/buildarea-sid/3.x.klose-debian-sparc/build/Lib/subprocess.py", line 1489, in wait
raise TimeoutExpired(self.args)
subprocess.TimeoutExpired: <unprintable TimeoutExpired object> ====================================================================== Traceback (most recent call last):
File "/home/pybot/buildarea-sid/3.x.klose-debian-sparc/build/Lib/test/test_subprocess.py", line 630, in test_wait_timeout
self.assertEqual(p.wait(timeout=2), 0)
File "/home/pybot/buildarea-sid/3.x.klose-debian-sparc/build/Lib/subprocess.py", line 1489, in wait
raise TimeoutExpired(self.args)
subprocess.TimeoutExpired: <unprintable TimeoutExpired object> ====================================================================== Traceback (most recent call last):
File "/home/pybot/buildarea-sid/3.x.klose-debian-sparc/build/Lib/test/test_subprocess.py", line 630, in test_wait_timeout
self.assertEqual(p.wait(timeout=2), 0)
File "/home/pybot/buildarea-sid/3.x.klose-debian-sparc/build/Lib/subprocess.py", line 1489, in wait
raise TimeoutExpired(self.args)
subprocess.TimeoutExpired: <unprintable TimeoutExpired object> ====================================================================== Traceback (most recent call last):
File "/home/pybot/buildarea-sid/3.x.klose-debian-sparc/build/Lib/test/test_subprocess.py", line 630, in test_wait_timeout
self.assertEqual(p.wait(timeout=2), 0)
File "/home/pybot/buildarea-sid/3.x.klose-debian-sparc/build/Lib/subprocess.py", line 1489, in wait
raise TimeoutExpired(self.args)
subprocess.TimeoutExpired: <unprintable TimeoutExpired object> ====================================================================== Traceback (most recent call last):
File "/home/pybot/buildarea-sid/3.x.klose-debian-sparc/build/Lib/test/test_subprocess.py", line 135, in test_check_output_timeout
self.assertEqual(c.exception.output, b'BDFL')
AssertionError: b'' != b'BDFL' ====================================================================== Traceback (most recent call last):
File "/home/pybot/buildarea-sid/3.x.klose-debian-sparc/build/Lib/test/test_subprocess.py", line 135, in test_check_output_timeout
self.assertEqual(c.exception.output, b'BDFL')
AssertionError: b'' != b'BDFL' ====================================================================== Traceback (most recent call last):
File "/home/pybot/buildarea-sid/3.x.klose-debian-sparc/build/Lib/test/test_subprocess.py", line 135, in test_check_output_timeout
self.assertEqual(c.exception.output, b'BDFL')
AssertionError: b'' != b'BDFL' ====================================================================== Traceback (most recent call last):
File "/home/pybot/buildarea-sid/3.x.klose-debian-sparc/build/Lib/test/test_subprocess.py", line 135, in test_check_output_timeout
self.assertEqual(c.exception.output, b'BDFL')
AssertionError: b'' != b'BDFL' http://www.python.org/dev/buildbot/all/builders/sparc%20Debian%203.x/builds/119 |
:( Thanks for spotting these. Is there an easier way for me to be notified if these particular tests fail? Some of these are not in the "stable" builder set. Sorry to leave the builders broken for so long. I just upped the timeouts to 3 seconds. I guess the issue is that the builders are slow and also heavily loaded, so processes just don't get to start up as quick as we'd like them too. It might be worth adding some plumbing to have the child process signal the parent when it's initialized, but that seems like it's going to add a whole bunch more complexity to the test. Will close in a few days if there are no more broken buildbots. |
Not really. There is no infrastructure to notify test failures to
Indeed, because they are not stable enough :) Thank you! |
All stable buildbots appear to be green, so closing... |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: