diff options
| author | Petr Viktorin <encukou@gmail.com> | 2024-01-18 02:15:29 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-17 17:15:29 -0800 |
| commit | c1db9606081bdbe0207f83a861a3c70c356d3704 (patch) | |
| tree | 4190826c9d57c68262ca8f294daad49820c75603 /Lib/test/test_multiprocessing_spawn/test_threads.py | |
| parent | e2c097ebdee447ded1109f99a235e65aa3533bf8 (diff) | |
| download | cpython-c1db9606081bdbe0207f83a861a3c70c356d3704.tar.gz cpython-c1db9606081bdbe0207f83a861a3c70c356d3704.zip | |
gh-113205: test_multiprocessing.test_terminate: Test the API on threadpools (#114186)
gh-113205: test_multiprocessing.test_terminate: Test the API works on threadpools
Threads can't be forced to terminate (without potentially corrupting too much
state), so the expected behaviour of `ThreadPool.terminate` is to wait for
the currently executing tasks to finish.
The entire test was skipped in GH-110848 (0e9c364f4ac18a2237bdbac702b96bcf8ef9cb09).
Instead of skipping it entirely, we should ensure the API eventually succeeds:
use a shorter timeout.
For the record: on my machine, when the test is un-skipped, the task manages to
start in about 1.5% cases.
Diffstat (limited to 'Lib/test/test_multiprocessing_spawn/test_threads.py')
0 files changed, 0 insertions, 0 deletions