Charles-François Natali added the comment:
This failure doesn't make sense: whether SIGALRM is delivered or not, epoll()
should time out after 2 seconds, not 105s.
What's more, here's another test_subprocess failure:
"""
======================================================================
ERROR: test_wait_timeout (test.test_subprocess.ProcessTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/var/lib/buildslave/3.x.murray-gentoo-wide/build/Lib/test/test_subprocess.py",
line 993, in test_wait_timeout
self.assertEqual(p.wait(timeout=3), 0)
File "/var/lib/buildslave/3.x.murray-gentoo-wide/build/Lib/subprocess.py",
line 1514, in wait
raise TimeoutExpired(self.args, timeout)
subprocess.TimeoutExpired: Command
'['/var/lib/buildslave/3.x.murray-gentoo-wide/build/python', '-c', 'import
time; time.sleep(0.3)']' timed out after 3 seconds
"""
Even more strange, a test_asyncio failure:
"""
======================================================================
FAIL: test_interrupted_retry (test.test_selectors.EpollSelectorTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/var/lib/buildslave/3.x.murray-gentoo-wide/build/Lib/test/test_selectors.py",
line 299, in test_interrupted_retry
self.assertLess(time() - t, 2.5)
AssertionError: 105.86884237639606 not less than 2.5
"""
asyncio uses selectors as backend, so let's admit the test fails, but what's
really surprising is that the timeout is *exactly* the same, up to the last
digit.
Something fishy is going on: David, did something change recently on that
buildbot?
----------
nosy: +r.david.murray
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue19386>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
