Skip to content

sequential.test-watch-mode-inspect seems flaky #49933

Description

@mhdawson

Test

sequential.test-watch-mode-inspect

Platform

Linux ARMv7

Console output

Error Message
fail (-15)
Stacktrace
---
duration_ms: 360029.938
exitcode: -15
severity: fail
...

Build links

Additional information

No response

Activity

added
flaky-testIssues and PRs involving tests that fail intermittently in CI.
on Sep 28, 2023
added
armIssues and PRs related to the ARM architecture.
on Sep 28, 2023

mhdawson commented on Sep 28, 2023

@mhdawson
MemberAuthor

Failed on same machine, two builds in a row
test-equinix-ubuntu2004_container-armv7l-1

mhdawson commented on Sep 28, 2023

@mhdawson
MemberAuthor

Passed when it ran on test-equinix-ubuntu2204-x64-2 so could be specific to that machine.

Need to track to see if it fails across the machines or not.

mhdawson commented on Sep 29, 2023

@mhdawson
MemberAuthor

Interestingly I see this in the output

not ok 3844 sequential/test-watch-mode-inspect # TODO : Fix flaky test

which seems to say it's a known issue even though I could not find a tracking issue.

richardlau commented on Sep 29, 2023

@richardlau
Member

FWIW the test is already marked flaky

# https://github.com/nodejs/node/issues/44898
test-watch-mode: PASS, FLAKY
test-watch-mode-inspect: PASS, FLAKY

https://ci.nodejs.org/job/node-test-binary-armv7l/7720/RUN_SUBSET=js,nodes=ubuntu2004-armv7l/console has failed because of leftover Node.js processes (which are probably related to the test being timed out):

17:02:09 All tests passed.
17:02:09 ps awwx | grep Release/node | grep -v grep | cat
17:02:09 2212632 ?        Sl     0:00 /home/iojs/build/workspace/node-test-binary-armv7l/out/Release/node --inspect=0 --watch /home/iojs/build/workspace/node-test-binary-armv7l/test/fixtures/watch-mode/inspect.js
17:02:09 2212638 ?        Sl     0:00 /home/iojs/build/workspace/node-test-binary-armv7l/out/Release/node --inspect=0 /home/iojs/build/workspace/node-test-binary-armv7l/test/fixtures/watch-mode/inspect.js
17:02:09 make: *** [Makefile:538: test-ci-js] Error 1

anonrig commented on Oct 17, 2023

@anonrig
Member

anonrig commented on Oct 18, 2023

@anonrig
Member

mhdawson commented on Oct 20, 2023

@mhdawson
MemberAuthor

I don't see if failing in https://ci.nodejs.org/job/node-test-commit-osx-arm/13900/, that seemed to be a different test test-watch-mode without the inspect part.

mhdawson commented on Nov 23, 2023

@mhdawson
MemberAuthor

12 remaining items

mhdawson commented on Feb 2, 2024

@mhdawson
MemberAuthor

jakecastelli commented on Jul 30, 2024

@jakecastelli
Member

Again - https://ci.nodejs.org/job/node-test-commit-smartos/nodes=smartos20-64/55713/

logs
22:09:53 not ok 4228 sequential/test-watch-mode-inspect # TODO : Fix flaky test
22:09:53   ---
22:09:53   duration_ms: 300129.29800
22:09:53   severity: fail
22:09:53   exitcode: -15
22:09:53   stack: |-
22:09:53     timeout
22:09:53     [test] Connecting to a child Node process
22:09:53     [test] Testing /json/list
22:09:53     TAP version 13
22:09:53     [err] Debugger listening on ws://127.0.0.1:61622/bec85c05-bcf7-4407-86de-720d30c10727
22:09:53     [err] For help, see: https://nodejs.org/en/docs/inspector
22:09:53     [err] 
22:09:53     [err] Debugger attached.
22:09:53     [err] 
22:09:53     [test] Connecting to a child Node process
22:09:53     [test] Testing /json/list
22:09:53     [err] Debugger ending on ws://127.0.0.1:61622/bec85c05-bcf7-4407-86de-720d30c10727
22:09:53     [err] For help, see: https://nodejs.org/en/docs/inspector
22:09:53     [err] 
22:09:53     [out] safe to debug now
22:09:53     [out] 
22:09:53   ...

This test seems to fail quite often lately

aduh95 commented on Sep 10, 2024

@aduh95
Contributor

github-actions commented on May 28, 2026

@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.

added
staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
on May 28, 2026
removed
staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
on May 28, 2026

github-actions commented on Aug 27, 2026

@github-actions
Contributor

This issue has been marked as stale due to 90 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.

added
staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Aug 27, 2026
removed
staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Aug 27, 2026
added
never-staleIssues and PRs exempt from automated stale handling.
on Aug 28, 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

    armIssues and PRs related to the ARM architecture.flaky-testIssues and PRs involving tests that fail intermittently in CI.never-staleIssues and PRs exempt from automated stale handling.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions