René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Test runner file exits with code 1 when awaiting tests + filtering","articleBody":"### Version\n\nv26.3.0\n\n### Platform\n\n```text\nMicrosoft Windows NT 10.0.26200.0 x64\n```\n\nalso reproduces under WSL:\n\n```\nLinux dell-xps-3 6.18.33.2-microsoft-standard-WSL2 #1 SMP PREEMPT_DYNAMIC Thu Jun 18 21:54:43 UTC 2026 x86_64 GNU/Linux\n```\n\n### Subsystem\n\nnode:test\n\n### What steps will reproduce the bug?\n\nWeird one to minify, here's what I got it down to:\n\n```js\nimport test from \"node:test\";\n\nawait test.suite(\"Suite A\", async (t) => {\n});\n\nawait test.suite(\"Suite B\", async (t) => {\n  await test(\"Test 1\", async () => {\n  });\n  await test(\"Test 2\", async () => {\n  });\n});\n\nawait test.suite(\"Suite C\", async () => {\n  await test(\"Test 3\", async () => {\n  });\n});\n```\n\nThen `node --test --test-name-pattern=C test.js` (or any other pattern than `B`) gives the following error output:\n\n```\n▶ Suite C\n  ✔ Test 3 (0.8439ms)\n✔ Suite C (1.0333ms)\n✖ test.js (54.3035ms)\nℹ tests 2\nℹ suites 1\nℹ pass 1\nℹ fail 1\nℹ cancelled 0\nℹ skipped 0\nℹ todo 0\nℹ duration_ms 59.748\n```\n\nAlso reproduces using `.only` rather than `--test-name-pattern`\n\nWithout `--test` it produces the following output, with an exit code of 1 - note the change to `cancelled`!:\n\n```\n▶ Suite C\n  ✔ Test 3 (0.175ms)\n✔ Suite C (1.024ms)\nℹ tests 2\nℹ suites 1\nℹ pass 1\nℹ fail 0\nℹ cancelled 1\nℹ skipped 0\nℹ todo 0\nℹ duration_ms 6.6097\n```\n\n`--trace-exit` does not list anything additional.\nLogging `exitCode` in `process.on(\"exit\")` is `1`.\n\nUsing `--test-reporter=tap` only lists expected `ok` tests without `--test`, with it it also lists:\n\n```\n# Subtest: test.js\nnot ok 1 - test.js\n  ---\n  duration_ms: 59.742\n  type: 'test'\n  location: 'D:\\\\scratch\\\\node-test-repro\\\\test.js:1:1'\n  failureType: 'testCodeFailure'\n  exitCode: 1\n  signal: ~\n  error: 'test failed'\n  code: 'ERR_TEST_FAILURE'\n  ...\n1..2\n```\n\nas expected.\n\nRemoving any of the awaits, from either suites or tests seems to resolve the issue.\n\n### How often does it reproduce? Is there a required condition?\n\nSeemingly reliably, though given it seems to be a timing related issue I can't promise that...\n\n### What is the expected behavior? Why is that the expected behavior?\n\nIt's quite possible there is some legitimate usage error here, but it should at least report what it is clearly, and certainly not only in such specific conditions!\n\nThe reason I'm using awaits in the tests in the suites is due to the editor / linter getting fussy about unawaited promises due to the types. This is a generally very handy check, so I'm loath to ignore it...\n\n### What do you see instead?\n\n(provided above)\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/simonbuchan","@type":"Person","name":"simonbuchan"},"datePublished":"2026-06-30T00:03:09Z","url":"https://github.com/nodejs/node/issues/64203"}