First reported in this comment on PR #25346 by @oscarbenjamin, it now seems that the Pyodide job (specifically job 3/4) is timing out on multiple PRs. Pytest is working correctly and exiting with exit code 0. The pyodide.runPython command is also completing. No changes have been made to the CI, so it must be to do with a Node or Pyodide change of some form, which is resulting in Node not successfully completing execution of the bin/test_pyodide.mjs script.

The script is being run in CI with the command:

run: node bin/test_pyodide.mjs --group=${{ matrix.group }} --splits=4 2>/dev/null  # ignore node exception`

It's not clear to be why we need the 2>/dev/null. @eagleoflqj can you provide any insight here?