Repository navigation
test-runner-watch-mode is flaky #49605
Description
| Reason | parallel/test-runner-watch-mode |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 5 (#49419, #49559, #49565, #49575, #49582) |
| Appeared | test-osuosl-ubuntu2004_container-armv7l-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53812/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53856/ |
Example
not ok 2874 parallel/test-runner-watch-mode
---
duration_ms: 360086.13100
severity: fail
exitcode: -15
stack: |-
timeout
TAP version 13
Updating /home/iojs/tmp/.tmp.2382/dependent.js
Updating /home/iojs/tmp/.tmp.2382/dependent.js
Updating /home/iojs/tmp/.tmp.2382/dependent.js
Updating /home/iojs/tmp/.tmp.2382/dependent.js
Updating /home/iojs/tmp/.tmp.2382/dependent.js
Updating /home/iojs/tmp/.tmp.2382/dependent.js
Updating /home/iojs/tmp/.tmp.2382/dependent.js
Updating /home/iojs/tmp/.tmp.2382/dependent.js
Updating /home/iojs/tmp/.tmp.2382/dependent.js
Updating /home/iojs/tmp/.tmp.2382/dependent.js
Updating /home/iojs/tmp/.tmp.2382/dependent.js
# Subtest: test runner watch mode
# Subtest: should run tests repeatedly
ok 1 - should run tests repeatedly
---
duration_ms: 1301.051293
...
Refs: nodejs/reliability#662
From the full log it looks like something is quite wrong in the test, it keeps getting stuck at tons of Updating /home/iojs/node-tmp/.tmp.2479/dependency.js until the 2 minute timeout is reached (my guess is it has more to do with how the test is written)
Activity
test: split test-runner-watch-mode
test: move test-runner-watch-mode helper into common
test: split test-runner-watch-mode
test: move test-runner-watch-mode helper into common
test: split test-runner-watch-mode
test: move test-runner-watch-mode helper into common
test: split test-runner-watch-mode
github-actions commentedon May 28, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jun 28, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
inoway46 commentedon Sep 14, 2026
This still seems to be flaky. Recent failures are hitting
should support a watched test file renamewithENOENTfromrenameSync().panva commentedon Sep 15, 2026
This is indeed resolved, the flakes are on the 22.x backport or daily v22.x CI runs. And the reports are inaccurate see nodejs/node-core-utils#1191.