You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Sporadic failure in test_dump_tracebacks_later_file (test_faulthandler) #60175
Traceback (most recent call last):
File "/Users/ambv/Buildbot/3.x.langa-lion/build/Lib/test/test_faulthandler.py", line 490, in test_dump_tracebacks_later_fileself.check_dump_tracebacks_later(file=True)
File "/Users/ambv/Buildbot/3.x.langa-lion/build/Lib/test/test_faulthandler.py", line 476, in check_dump_tracebacks_later
filename, loops)
File "/Users/ambv/Buildbot/3.x.langa-lion/build/Lib/test/test_faulthandler.py", line 460, in _check_dump_tracebacks_laterself.assertRegex(trace, regex)
AssertionError: Regex didn't match: '^Timeout \\(0:00:00.500000\\)!\\nThread 0x[0-9a-f]+:\\n File "<string>", line 9 in func\n File "<string>", line 20 in <module>$' not found in 'Timeout (0:00:00.500000)!\nThread 0x00007fff77d85960:\n File "<string>", line 10 in func\n File "<string>", line 20 in <module>'
Ran 30 tests in 126.504s
The regex expects the failure to be at "line 9 in func", but the failure happens at "line 10".
If the test fails at line 10: it means that it failed to dump the
traceback in 2.5 seconds, whereas the traceback must be dumped after a
timeout of 0.5 second.
Do you know if the system load of this particular buildbot is high? It
would be nice to have the system load in the output of the buildbot.
We might change the timeout, but it is already long.
Activity
ezio-melotti commentedon Sep 19, 2012
Seen on http://buildbot.python.org/all/builders/AMD64%20Lion%203.x/builds/428/steps/test/logs/stdio
======================================================================
FAIL: test_dump_tracebacks_later_file (test.test_faulthandler.FaultHandlerTests)
----------------------------------------------------------------------
Ran 30 tests in 126.504s
The regex expects the failure to be at "line 9 in func", but the failure happens at "line 10".
vstinner commentedon Sep 19, 2012
Code of the failing test:
----
If the test fails at line 10: it means that it failed to dump the
traceback in 2.5 seconds, whereas the traceback must be dumped after a
timeout of 0.5 second.
Do you know if the system load of this particular buildbot is high? It
would be nice to have the system load in the output of the buildbot.
We might change the timeout, but it is already long.
vstinner commentedon Mar 25, 2014
I didn't see this error recently.