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

[colesbury]

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).

https://bugs.python.org/issue46205

[colesbury]

@vstinner, this is the simplest fix, but I'm not sure it's ideal. There are still potential race conditions between checking if any workers are alive and reading from the output queue. This means that there can be up to an extra 30 second delay (instead of an hanging forever), while waiting for self.output.get().

Here's an alternative approach that uses a sentinel worker value: colesbury@406e5d7. I'm a little worried about the more complicated approach because it looks like hangs have been an issue in the past, and I'm worried about introducing new bugs. Let me know which approach you think is better.

[corona10]

lgtm

[miss-islington]

Thanks @colesbury for the PR, and @corona10 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9, 3.10.
🐍🍒⛏🤖

[bedevere-bot]

GH-30523 is a backport of this pull request to the 3.10 branch.

[bedevere-bot]

GH-30524 is a backport of this pull request to the 3.9 branch.

[vstinner]

Thanks for the fix @colesbury!