Skip to content
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

TST: Use safer context for ProcessPoolExecutor #8715

Merged
merged 1 commit into from
Jun 25, 2024
Merged

Commits on Jun 24, 2024

  1. TST: Use safer context for ProcessPoolExecutor

    When running `test_process_executor_kills_process` just by itself, I get
    a warning that threads have been used and that the `fork`
    multiprocessing context is unsafe. If I run the full test suite, then
    the same test hangs.
    
    I don't know where the threads are coming from (as I didn't use xdist),
    but explicitly use distributed's default context (which is the safer
    `spawn` multiprocess context) to avoid these issues.
    QuLogic committed Jun 24, 2024
    Configuration menu
    Copy the full SHA
    efb95e4 View commit details
    Browse the repository at this point in the history