Uh oh!
There was an error while loading. Please reload this page.
gh-109276: libregrtest: WASM use stdout for JSON - #109355
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
3dde8e4 to
23aa839CompareOn 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
6bd1482Comparevstinner
commented
Sep 12, 2023
!buildbot wasm32 |
bedevere-bot
commented
Sep 12, 2023
🤖 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:
|
vstinner
commented
Sep 13, 2023
Failures on wasm32-wasi: I suppose that these failures are related to the following warnings: |
bedevere-bot
commented
Sep 13, 2023
|
vstinner
commented
Sep 13, 2023
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.