Commit 569182c
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.
Use shorter sleep time for threadpools, so if a task manages to start, the test
doesn't block for long.
(cherry picked from commit c1db960)
Co-authored-by: Petr Viktorin <[email protected]>
1 parent 363dddb commit 569182c
1 file changed
+9
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2693 | 2693 | | |
2694 | 2694 | | |
2695 | 2695 | | |
| 2696 | + | |
| 2697 | + | |
| 2698 | + | |
| 2699 | + | |
| 2700 | + | |
| 2701 | + | |
| 2702 | + | |
| 2703 | + | |
2696 | 2704 | | |
2697 | | - | |
| 2705 | + | |
2698 | 2706 | | |
2699 | 2707 | | |
2700 | 2708 | | |
| |||
0 commit comments