gh-84461: Add ability for multiprocessed libregrtest to use a different Python executable#91930
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
wasm32-emscripten does not support subprocesses. As a workaround, we can run the regression test suite with e.g. the system-native Python used for cross building, then execute the actual subprocess workers with the emscripten/target runtime.
For example, consider a setup where you have two folders:
linux, which includes a build of CPython for linux and the native architecture of the machine. You also havewasm, which is the cross compiled Python for emscripten/node.This PR would enable you to do
linux/python -m test -j1 -p "node wasm/python.js", to run the test suite workers in nodejs.