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_multiprocessing_fork failures #63631
Comments
I'm getting the following test_multiprocessing_fork failures on Debian test_default_timeout (test.test_multiprocessing_fork.WithThreadsTestBarrier) ... Exception in thread Thread-344:
Traceback (most recent call last):
File "/home/stefan/hg/master3/Lib/threading.py", line 921, in _bootstrap_inner
self.run()
File "/home/stefan/hg/master3/Lib/threading.py", line 869, in run
self._target(*self._args, **self._kwargs)
File "/home/stefan/hg/master3/Lib/test/_test_multiprocessing.py", line 1152, in task
self.f(*self.args)
File "/home/stefan/hg/master3/Lib/test/_test_multiprocessing.py", line 1382, in _test_default_timeout_f
barrier.wait()
File "/home/stefan/hg/master3/Lib/threading.py", line 616, in wait
self._wait(timeout)
File "/home/stefan/hg/master3/Lib/threading.py", line 653, in _wait
self._break()
File "/home/stefan/hg/master3/Lib/threading.py", line 702, in _break
self._cond.notify_all()
File "/home/stefan/hg/master3/Lib/threading.py", line 359, in notify_all
self.notify(len(self._waiters))
File "/home/stefan/hg/master3/Lib/threading.py", line 342, in notify
waiters_to_notify = _deque(_islice(all_waiters, n))
RuntimeError: deque mutated during iteration FAIL ====================================================================== Traceback (most recent call last):
File "/home/stefan/hg/master3/Lib/test/_test_multiprocessing.py", line 1393, in test_default_timeout
self.assertEqual(len(results), barrier.parties)
AssertionError: 4 != 5 |
The issue is probably different from bpo-19227, since it already occurs |
This is a test of threading.Barrier rather than anything implemented directly by multiprocessing. Tests which involve timeouts tend to be a bit flaky. Increasing the length of timeouts usually helps, but makes the tests take even longer. How often have you seen this failure? Did it happen on a buildbot? Was there a lot of other activity on the system at the time? |
I've seen the failure very often, without any particular load. Now I noticed that during test_tools there were several ksoftirqd test_multiprocessing_fork no longer fails. |
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: