-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
gh-109276: libregrtest: WASM use stdout for JSON #109355
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
3dde8e4
to
23aa839
Compare
On Emscripten and WASI, or if --python command line is used, libregrtest now writes JSON into stdout, instead of using a name file. * Add JsonFileType.STDOUT. * Remove JsonFileType.FILENAME. * test.pythoninfo logs environment variables related to cross-compilation and running Python on Emscripten/WASI.
23aa839
to
6bd1482
Compare
!buildbot wasm32 |
🤖 New build scheduled with the buildbot fleet by @vstinner for commit 6bd1482 🤖 The command will test the builders whose names match following regular expression: The builders matched are:
|
Failures on wasm32-wasi:
I suppose that these failures are related to the following warnings:
|
|
I wrote PR #109356 to fix the WASI platform. |
On Emscripten and WASI, or if --python command line is used, libregrtest now writes JSON into stdout, instead of using a name file. * Add JsonFileType.STDOUT. * Remove JsonFileType.FILENAME. * test.pythoninfo logs environment variables related to cross-compilation and running Python on Emscripten/WASI.
On Emscripten and WASI, or if --python command line is used, libregrtest now writes JSON into stdout, instead of using a name file.