Skip to content

test-runner-watch-mode is flaky #49605

Closed
Closed
test-runner-watch-mode is flaky#49605
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.test_runnerIssues and PRs related to the test runner subsystem.

Description

@joyeecheung
joyeecheung
opened on Sep 11, 2023
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)

https://ci.nodejs.org/job/node-test-binary-armv7l/7355/RUN_SUBSET=js,nodes=ubuntu2004-armv7l/consoleText

Activity

  1. joyeecheung commented on Sep 11, 2023

    @joyeecheung
    joyeecheung
    on Sep 11, 2023
    MemberAuthor

    cc @nodejs/test_runner

  2. joyeecheung
    added
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    on Sep 11, 2023

  3. MoLow commented on Sep 11, 2023

    @MoLow
    MoLow
    on Sep 11, 2023
    Member

    is anyone able to reproduce with tools/test.py --repeat=1000 test/parallel/test-runner-watch-mode.mjs? on my machine it passes smoothly

  4. aduh95 commented on Sep 11, 2023

    @aduh95
    aduh95
    on Sep 11, 2023 via email
    Contributor

  5. joyeecheung commented on Sep 11, 2023

    @joyeecheung
    joyeecheung
    on Sep 11, 2023
    MemberAuthor

    The flakes in the CI only show up in Linux ARM and Linux + shared library. I am guessing using a similar setup may help reproducing the issues. Or you can try using the the CI boxes.

  6. joyeecheung commented on Sep 11, 2023

    @joyeecheung
    joyeecheung
    on Sep 11, 2023
    MemberAuthor

    Looks like this also comes up to people running Ubuntu 22.04 locally too #49513

  7. nodejs-github-bot
    added a commit that references this issue on Sep 14, 2023

    test: mark test-runner-watch-mode as flaky

    b289c6d
  8. joyeecheung
    added
    test_runnerIssues and PRs related to the test runner subsystem.
    on Sep 25, 2023
  9. ruyadorno
    added a commit that references this issue on Sep 28, 2023

    test: mark test-runner-watch-mode as flaky

    ab3afb3
  10. targos
    added a commit that references this issue on Nov 27, 2023

    test: mark test-runner-watch-mode as flaky

    5df2352
  11. sercher
    added 2 commits that reference this issue on Apr 25, 2024

    test: mark test-runner-watch-mode as flaky

    6305d66

    test: mark test-runner-watch-mode as flaky

    2201bcf

  12. aduh95 commented on Aug 15, 2024

    @aduh95
    aduh95
    on Aug 15, 2024
    Contributor

    Happened again on https://ci.nodejs.org/job/node-test-commit-linuxone/45127/nodes=rhel8-s390x/

  13. nodejs-github-bot
    added a commit that references this issue on Oct 28, 2025

    test: move test-runner-watch-mode helper into common

    028ad5e

  14. 3 remaining items

  15. aduh95
    added 4 commits that reference this issue on Nov 11, 2025

    test: move test-runner-watch-mode helper into common

    7f40630

    test: split test-runner-watch-mode

    4029747

    test: move test-runner-watch-mode helper into common

    e78e0cf

    test: split test-runner-watch-mode

    bbca575

  16. github-actions commented on May 28, 2026

    @github-actions
    github-actionsbot
    on May 28, 2026 – with GitHub Actions
    Contributor

    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.

  17. github-actions
    added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on May 28, 2026

  18. github-actions commented on Jun 28, 2026

    @github-actions
    github-actionsbot
    on Jun 28, 2026 – with GitHub Actions
    Contributor

    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.

  19. github-actions
    closed this as not plannedon Jun 28, 2026

  20. inoway46 commented on Sep 14, 2026

    @inoway46
    inoway46
    on Sep 14, 2026
    Contributor

    This still seems to be flaky. Recent failures are hitting should support a watched test file rename with ENOENT from renameSync().

  21. inoway46
    reopened this on Sep 14, 2026
  22. inoway46
    added
    never-staleIssues and PRs exempt from automated stale handling.
    and removed
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Sep 14, 2026
  23. panva
    removed
    never-staleIssues and PRs exempt from automated stale handling.
    on Sep 15, 2026

  24. panva commented on Sep 15, 2026

    @panva
    panva
    on Sep 15, 2026
    Member

    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.

  25. panva
    closed this as completedon Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    flaky-testIssues and PRs involving tests that fail intermittently in CI.test_runnerIssues and PRs related to the test runner subsystem.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions