This needs a bit more code, so absent any performance speedup, I'd prefer the previous version. My assumption was that the fuzzing happens in the subprocess, so any python GIL "deadlocks" in the thread pool won't have any performance effect on the subprocess itself. I might be wrong, though.

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts

Reviewers, this pull request conflicts with the following ones:

• doc: [test] Remove outdated comment in fuzz runner #20759 (doc: [test] Remove outdated comment in fuzz runner by MarcoFalke)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

🐙 This pull request conflicts with the target branch and needs rebase.

_{Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".}

• Is it still relevant? ➡️ Please solve the conflicts to make it ready for review and to ensure the CI passes.
• Is it no longer relevant? ➡️ Please close.
• Did the author lose interest or time to work on this? ➡️ Please close it and mark it 'Up for grabs' with the label, so that it can be picked up in the future.