Intermittent failure in inspector/test-break-when-eval ? #14982

Activity

1. mscdex

   added

   inspectorIssues and PRs related to the V8 inspector protocol.Issues and PRs related to the V8 inspector protocol.

   testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.

   on Aug 22, 2017
2. Trott commented on Aug 23, 2017

   

   Trott

   on Aug 23, 2017

   Member

   More actions

   Uh oh, here's another one:

   https://ci.nodejs.org/job/node-test-commit-linux/12004/nodes=centos5-32/console

   not ok 1597 inspector/test-break-when-eval
     ---
     duration_ms: 15.536
     severity: fail
     stack: |-
       [test] Connecting to a child Node process
       [test] Testing /json/list
       [err] Debugger listening on ws://127.0.0.1:40127/671264a9-152c-478d-9198-afc2c1312d50
       [err] For help see https://nodejs.org/en/docs/inspector
       [err] 
       [test] Setting up a debugger
       [err] Debugger attached.
       [err] 
       [test] Breaking in the code
       [out] Ready!
       [out] 
       [test] Step over console statement and test output
       [out] 0 3
       [out] 
       Timed out waiting for matching notification (Console output matching [0,3]))
       1
3. Trott commented on Aug 23, 2017

   

   Trott

   on Aug 23, 2017

   Member

   More actions

   @nodejs/v8-inspector
4. eugeneo

   self-assigned this

   on Aug 24, 2017
5. eugeneo commented on Aug 24, 2017

   

   eugeneo

   on Aug 24, 2017

   Contributor

   More actions

   Status update: I am looking into it but this seems to be an actual bug (console.log is not reported to the front end randomly) and not just a test issue. Looks like other platforms do not see this, on CentOS there was 1 failure out of 100 runs.

   I don't know how long it will take to fix this... Should I mark the test flaky for now?
6. Trott commented on Oct 1, 2017

   

   Trott

   on Oct 1, 2017

   Member

   More actions

   I saw this again today, on CentOS 5 as usual. I guess we can add this as another data point for "something is up with CentOS 5, it's EOL anyway, let's remove it from CI". See nodejs/build#898
7. Trott commented on Oct 4, 2017

   

   Trott

   on Oct 4, 2017

   Member

   More actions

   Alas, saw this on ubuntu 1604-32:

   https://ci.nodejs.org/job/node-test-commit-linux/12833/nodes=ubuntu1604-32/console

   not ok 1808 inspector/test-break-when-eval
     ---
     duration_ms: 15.577
     severity: fail
     stack: |-
       [test] Connecting to a child Node process
       [test] Testing /json/list
       [err] Debugger listening on ws://127.0.0.1:35244/3e7b9b63-c42e-4de8-842f-d2035367feaa
       [err] 
       [err] For help see https://nodejs.org/en/docs/inspector
       [err] 
       [test] Setting up a debugger
       [err] Debugger attached.
       [err] 
       [test] Breaking in the code
       [out] Ready!
       [out] 
       [test] Step over console statement and test output
       [out] 0 3
       [out] 
       Timed out waiting for matching notification (Console output matching [0,3]))
       1
     ...
8. maclover7

   added

   flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.

   on Dec 25, 2017
9. Trott commented on Oct 18, 2018

   

   Trott

   on Oct 18, 2018

   Member

   More actions

   This test is now in sequential and has a slightly different name. Seems likely it's not flaky anymore. Closeing.
10. Trott

    closed this as completedon Oct 18, 2018