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.

Sign up for GitHub

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

Jump to bottom

bpo-46205: exit if no workers are alive in runtest_mp #30470

Merged
merged 2 commits into from
Jan 11, 2022
Merged

bpo-46205: exit if no workers are alive in runtest_mp #30470

merged 2 commits into from
Jan 11, 2022

Commits on Jan 7, 2022

  1. bpo-46205: exit if no workers are alive in runtest_mp 

    There is a race condition in runtest_mp where if a worker already
pushed its final output to the queue, but is still alive, then the
the main thread waits forever on the the now-empty queue.

This re-checks the status of the workers after output.get() call times
out (after 30 seconds).
    @colesbury
    colesbury committed Jan 7, 2022
    Configuration menu
    Copy the full SHA
    a459729 View commit details
    Browse the repository at this point in the history

Commits on Jan 10, 2022

  1. Refactor _get_result() based on @corona10's suggestion.

    @colesbury
    colesbury committed Jan 10, 2022
    Configuration menu
    Copy the full SHA
    5827e28 View commit details
    Browse the repository at this point in the history