gh-84461: Add ability for multiprocessed libregrtest to use a different Python executable#91930
Conversation
|
@ethanhs can you add a news file? |
|
@ethanhs: Status check is done, and it's a success ✅ . |
1 similar comment
|
@ethanhs: Status check is done, and it's a success ✅ . |
|
Sorry, I can't merge this PR. Reason: |
|
@ethanhs: Status check is done, and it's a success ✅ . |
|
Sorry, I can't merge this PR. Reason: |
1 similar comment
|
Sorry, I can't merge this PR. Reason: |
|
@ethanhs: Status check is done, and it's a success ✅ . |
2 similar comments
|
@ethanhs: Status check is done, and it's a success ✅ . |
|
@ethanhs: Status check is done, and it's a success ✅ . |
|
Sorry, I can't merge this PR. Reason: |
2 similar comments
|
Sorry, I can't merge this PR. Reason: |
|
Sorry, I can't merge this PR. Reason: |
|
@ethanhs: Status check is done, and it's a success ✅ . |
|
Sorry, I can't merge this PR. Reason: |
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.