Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
gh-109276: libregrtest: WASM use filename for JSON#109326
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.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
359d425
toc45529b
Compare!buildbot wasm32 |
bedevere-bot commentedSep 12, 2023
🤖 New build scheduled with the buildbot fleet by@vstinner for commitc45529b 🤖 The command will test the builders whose names match following regular expression: The builders matched are:
|
Emscripten/WASI still use a file descriptor. It makes no sense to me :-( I'm not sure if buildbots got the right commit. |
On Emscripten and WASI platforms, libregrtest now uses a filename forthe JSON file. Passing a file descriptor to a child process doesn'twork on these platforms.
ee0cac8
to9c052ba
Compare!buildbot wasm32 |
bedevere-bot commentedSep 12, 2023
🤖 New build scheduled with the buildbot fleet by@vstinner for commit9c052ba 🤖 The command will test the builders whose names match following regular expression: The builders matched are:
|
!buildbot wasm32 |
bedevere-bot commentedSep 12, 2023
🤖 New build scheduled with the buildbot fleet by@vstinner for commit9c052ba 🤖 The command will test the builders whose names match following regular expression: The builders matched are:
|
wasm32-emscripten node (dynamic linking) PR failed with:
wasm32-wasi PR failed with:
|
I just merged PR#109337 which collect more data in test.support and test.support sub-modules. |
wasm32-emscripten node (dynamic linking) 3.x: test.pythoninfo,support.is_emscripten: True andsys.platform: emscripten as expected.
wasm32-emscripten node (pthreads) 3.x: test.pythoninfo,support.is_emscripten: True andsys.platform: emscripten as expected
wasm32-wasi 3.x: test.pythoninfo,support.is_wasi: True andsys.platform: wasi as expected
|
!buildbot wasm32 |
bedevere-bot commentedSep 12, 2023
🤖 New build scheduled with the buildbot fleet by@vstinner for commitc436370 🤖 The command will test the builders whose names match following regular expression: The builders matched are:
|
!buildbot wasm32 |
bedevere-bot commentedSep 12, 2023
🤖 New build scheduled with the buildbot fleet by@vstinner for commit4c8d5c8 🤖 The command will test the builders whose names match following regular expression: The builders matched are:
|
!buildbot wasm32 |
bedevere-bot commentedSep 12, 2023
🤖 New build scheduled with the buildbot fleet by@vstinner for commit4e2cfab 🤖 The command will test the builders whose names match following regular expression: The builders matched are:
|
Ok, I wrote a clean fix from this debug PR: PR#109340. |
wasm32-wasi PR failed: the WASI test worker process doesn't seem to have access to
|
I merged this PR instead of this DEBUG PR. |
Uh oh!
There was an error while loading.Please reload this page.
On Emscripten and WASI platforms, libregrtest now uses a filename for the JSON file. Passing a file descriptor to a child process doesn't work on these platforms.