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
Finally, I've managed to reproduce the deadlock by
# This script is in fish shellforIin$(seq 100)echo ===== Attempt $I =====
timeout 300 ./python -X dev -m test -j4 test_concurrent_futures -v
iftest$status -ne 0
echo"TEST FAILED!"break
end
end | tee /tmp/out.log
Here's the setup from the test output:
== CPython 3.14.0a0 (heads/main:dc03ce797a, Jul 13 2024, 09:48:51) [GCC 13.3.0]
== Linux-6.8.12-amd64-x86_64-with-glibc2.38 little-endian
== Python build: debug
== cwd: /home/ziima/git/cpython/build/test_python_worker_1032543æ
== CPU count: 4
== encodings: locale=UTF-8 FS=utf-8
== resources: all test resources are disabled, use -u option to unskip tests
From my observations it seems to occur more often if I run tests on the whole test_concurrent_futures (or complete tests) than just test_concurrent_futures.test_deadlock. Tests are running on all 4 cores on my notebook.
@encukou It doesn't seem to me that -X dev provides any useful info in this case. If you have any more suggestions on how to debug it, I'm all ears.
Bug report
Bug description:
Found at EuroPython 24 sprints.
sometimes ends up hanging on
Also occurs on @stinovlas machine (Debian or Ubuntu). More details when I'll be reproduce deadlock again.
CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux
The text was updated successfully, but these errors were encountered: