Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate flaky sequential/test-inspector-break-when-eval #21725

Closed
Trott opened this issue Jul 9, 2018 · 3 comments
Closed

Investigate flaky sequential/test-inspector-break-when-eval #21725

Trott opened this issue Jul 9, 2018 · 3 comments
Assignees
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI. inspector Issues and PRs related to the V8 inspector protocol

Comments

@Trott
Copy link
Member

Trott commented Jul 9, 2018

  • Version: v11.0.0-pre (master)
  • Platform: win10 vs2017
  • Subsystem: test inspector

https://ci.nodejs.org/job/node-test-binary-windows/18435/COMPILED_BY=vs2017,RUNNER=win10,RUN_SUBSET=2/console

03:46:08 not ok 568 sequential/test-inspector-break-when-eval
03:46:08   ---
03:46:08   duration_ms: 0.426
03:46:08   severity: fail
03:46:08   exitcode: 1
03:46:08   stack: |-
03:46:08     [test] Connecting to a child Node process
03:46:08     [test] Testing /json/list
03:46:08     [err] Debugger listening on ws://127.0.0.1:63764/ce7a415f-e235-4e76-9b07-378faa517c97
03:46:08     [err] For help, see: https://nodejs.org/en/docs/inspector
03:46:08     [err] 
03:46:08     [out] Ready!
03:46:08     [out] 
03:46:08     [test] Setting up a debugger
03:46:08     [test] Breaking in the code
03:46:08     [test] Step over console statement and test output
03:46:08     [out] 0 3
03:46:08     [out] 
03:46:08     [test] Verify node waits for the frontend to disconnect
03:46:08     [err] Debugger attached.
03:46:08     [err] Waiting for the debugger to disconnect...
03:46:08     [err] 
03:46:08     { AssertionError [ERR_ASSERTION]: Input A expected to strictly equal input B:
03:46:08     + expected - actual
03:46:08     
03:46:08     - 0
03:46:08     + 3221225477
03:46:08         at runTests (c:\workspace\node-test-binary-windows\test\sequential\test-inspector-break-when-eval.js:65:10)
03:46:08         at process._tickCallback (internal/process/next_tick.js:68:7)
03:46:08       generatedMessage: true,
03:46:08       name: 'AssertionError [ERR_ASSERTION]',
03:46:08       code: 'ERR_ASSERTION',
03:46:08       actual: 0,
03:46:08       expected: 3221225477,
03:46:08       operator: 'strictEqual' }
03:46:08     1
03:46:08   ...

@nodejs/testing @nodejs/platform-windows @nodejs/v8-inspector @nodejs/build

@Trott Trott added inspector Issues and PRs related to the V8 inspector protocol flaky-test Issues and PRs related to the tests with unstable failures on the CI. labels Jul 9, 2018
@addaleax
Copy link
Member

addaleax commented Jul 9, 2018

Side note: #21182 is a large-ish refactor of some of the inspector code, so it might make sense to re-check all flaky inspector tests after that?

@eugeneo
Copy link
Contributor

eugeneo commented Jul 10, 2018

Still failing with that change, but the failure is different. I will make sure that change fixes it.

@eugeneo eugeneo self-assigned this Jul 10, 2018
@eugeneo
Copy link
Contributor

eugeneo commented Jul 11, 2018

https://ci.nodejs.org/job/node-stress-single-test/nodes=win10-vs2017/1952/ - 1000 runs, no failures. I am hoping to land #21182 by the end of the week.

targos pushed a commit that referenced this issue Jul 14, 2018
Workers debugging will require interfacing between the "main" inspector
and per-worker isolate inspectors. This is consistent with what WS
interface does. This change is a refactoring change and does not change
the functionality.

PR-URL: #21182
Fixes: #21725
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Trott pushed a commit to Trott/io.js that referenced this issue Jul 15, 2018
Workers debugging will require interfacing between the "main" inspector
and per-worker isolate inspectors. This is consistent with what WS
interface does. This change is a refactoring change and does not change
the functionality.

PR-URL: nodejs#21182
Fixes: nodejs#21725
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI. inspector Issues and PRs related to the V8 inspector protocol
Projects
None yet
Development

No branches or pull requests

3 participants