-
-
Notifications
You must be signed in to change notification settings - Fork 30k
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_stress_delivery_dependent() of test_signal randomly fails on AMD64 Debian root 3.6/3.x #75032
Comments
Antoine: I told you that such stess-test is going to require work to polish it. So here is another example of failure. Enjoy :-) http://buildbot.python.org/all/builders/AMD64%20Debian%20root%203.6/builds/534/steps/test/logs/stdio == CPython 3.6.2rc1+ (heads/3.6:580cd5c, Jul 5 2017, 00:47:42) [GCC 4.9.2] Traceback (most recent call last):
File "/root/buildarea/3.6.angelico-debian-amd64/build/Lib/test/test_signal.py", line 1053, in test_stress_delivery_dependent
self.assertEqual(len(sigs), N, "Some signals were lost")
AssertionError: 4602 != 10000 : Some signals were lost ====================================================================== Traceback (most recent call last):
File "/root/buildarea/3.6.angelico-debian-amd64/build/Lib/test/test_signal.py", line 1086, in test_stress_delivery_simultaneous
self.assertEqual(len(sigs), N, "Some signals were lost")
AssertionError: 8206 != 10000 : Some signals were lost |
Another fail. The test pass when run again later. http://buildbot.python.org/all/builders/AMD64%20Debian%20root%203.6/builds/538/steps/test/logs/stdio ====================================================================== Traceback (most recent call last):
File "/root/buildarea/3.6.angelico-debian-amd64/build/Lib/test/test_signal.py", line 1053, in test_stress_delivery_dependent
self.assertEqual(len(sigs), N, "Some signals were lost")
AssertionError: 4073 != 10000 : Some signals were lost |
Hey Antoine, as expected, your test fails randomly on the CI :-( Another failure: test_stress_delivery_dependent (test.test_signal.StressTest) ... Timeout (0:15:00)! |
Hmm. Perhaps someone can give me temporary shell access to one of those buildbots? |
Antoine: "Hmm. Perhaps someone can give me temporary shell access to one of those buildbots?" Contact directly the owners:
|
Check your @python.org inbox. |
Victor, Zachary, http://buildbot.python.org/all/builders/x86%20Gentoo%20Non-Debug%20with%20X%203.x/builds/830 corresponds to a very old changeset (more than one month old) before itimer() was fixed in 729780a. |
Oh, Zach's Gentoo buildbot was offline for a long time. Maybe it ran tests |
test_stress_delivery_dependent() failed on AMD64 Debian root 3.x too, it's not specific to 3.6: |
Recent failure on AMD64 Debian root 3.7: http://buildbot.python.org/all/#/builders/127/builds/361 0:03:33 load avg: 1.38 [140/415/1] test_signal failed ====================================================================== Traceback (most recent call last):
File "/root/buildarea/3.7.angelico-debian-amd64/build/Lib/test/test_signal.py", line 1116, in test_stress_delivery_dependent
self.assertEqual(len(sigs), N, "Some signals were lost")
AssertionError: 3586 != 10000 : Some signals were lost ====================================================================== Traceback (most recent call last):
File "/root/buildarea/3.7.angelico-debian-amd64/build/Lib/test/test_signal.py", line 1149, in test_stress_delivery_simultaneous
self.assertEqual(len(sigs), N, "Some signals were lost")
AssertionError: 8884 != 10000 : Some signals were lost |
I can reproduce the failure on multiple OSes in VirtaulBox when run test_signal in parallel with test_regrtest: ./python -m test -j2 test_signal test_regrtest test_regrtest test_regrtest
Run tests in parallel using 2 child processes
0:00:29 load avg: 4.24 [1/4] test_regrtest passed
0:00:58 load avg: 4.96 [2/4] test_regrtest passed -- running: test_signal (58 sec 728 ms)
0:01:00 load avg: 4.96 [3/4/1] test_signal failed
test test_signal failed -- Traceback (most recent call last):
File "/home/serhiy/py/cpython3.7/Lib/test/test_signal.py", line 1116, in test_stress_delivery_dependent
self.assertEqual(len(sigs), N, "Some signals were lost")
AssertionError: 5073 != 10000 : Some signals were lost But can't reproduce on hardware. |
After increasing the number of CPUs in the virtual machine the failure no longer reproduced. It is reproducible only with a single CPU. |
The test just failed on AMD64 Debian root 3.x and according to test.pythoninfo, this machine has a single CPU: os.cpu_count: 1 http://buildbot.python.org/all/#/builders/27/builds/1247 ... Traceback (most recent call last):
File "/root/buildarea/3.x.angelico-debian-amd64/build/Lib/test/test_signal.py", line 1156, in test_stress_delivery_dependent
self.assertEqual(len(sigs), N, "Some signals were lost")
AssertionError: 3617 != 10000 : Some signals were lost |
I didn't see this failure recently, I close the issue. |
We also got this error randomly on an internal s390x Red Hat build server: ====================================================================== Traceback (most recent call last):
File "/usr/lib64/python3.9/test/test_signal.py", line 1245, in test_stress_delivery_simultaneous
self.assertEqual(len(sigs), N, "Some signals were lost")
AssertionError: 5936 != 10000 : Some signals were lost |
I reopen the issue, the test still fails randomly on AMD64 Debian root 3.x: https://buildbot.python.org/all/#/builders/345/builds/5878 |
See also issue gh-110083: test_signal: test_stress_modifying_handlers() crash with SIGSEGV on GHA macOS (macOS-12.7). |
Now that tests are re-run in verbose mode when they fail, the test no longer makes a whole test suite to be marked as failed. I close the issue again, so nobody seems to be eagger to fix the test or the code. |
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: