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

parallel.test-inspector-async-hook-setup-at-inspect-brk is flaky #50222

Closed
anonrig opened this issue Oct 17, 2023 · 1 comment
Closed

parallel.test-inspector-async-hook-setup-at-inspect-brk is flaky #50222

anonrig opened this issue Oct 17, 2023 · 1 comment
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI. linux Issues and PRs related to the Linux platform. s390 Issues and PRs related to the s390 architecture.

Comments

@anonrig
Copy link
Member

anonrig commented Oct 17, 2023

Test

parallel.test-inspector-async-hook-setup-at-inspect-brk

Platform

Linux s390x

Console output

not ok 1881 parallel/test-inspector-async-hook-setup-at-inspect-brk
  ---
  duration_ms: 15398.43700
  severity: fail
  exitcode: 1
  stack: |-
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:37321/8bbe9463-d7c0-45fe-a855-99542b3099c0
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [err] Debugger attached.
    [err] 
    Timed out waiting for matching notification (break on [eval]:1)
    1
  ...

Build links

Additional information

No response

@anonrig anonrig added the flaky-test Issues and PRs related to the tests with unstable failures on the CI. label Oct 17, 2023
@github-actions github-actions bot added the linux Issues and PRs related to the Linux platform. label Oct 17, 2023
@anonrig anonrig added the s390 Issues and PRs related to the s390 architecture. label Oct 17, 2023
anonrig added a commit to anonrig/node that referenced this issue Oct 18, 2023
nodejs-github-bot pushed a commit that referenced this issue Oct 18, 2023
Ref: #50222
PR-URL: #50252
Refs: #50222
Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
targos pushed a commit that referenced this issue Oct 23, 2023
Ref: #50222
PR-URL: #50252
Refs: #50222
Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
alexfernandez pushed a commit to alexfernandez/node that referenced this issue Nov 1, 2023
Ref: nodejs#50222
PR-URL: nodejs#50252
Refs: nodejs#50222
Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
targos pushed a commit that referenced this issue Nov 11, 2023
Ref: #50222
PR-URL: #50252
Refs: #50222
Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
targos pushed a commit that referenced this issue Nov 27, 2023
Ref: #50222
PR-URL: #50252
Refs: #50222
Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
@lpinca
Copy link
Member

lpinca commented Feb 24, 2024

Should be fixed by 0161ad0.

@lpinca lpinca closed this as completed Feb 24, 2024
sercher added a commit to sercher/graaljs that referenced this issue Apr 25, 2024
Ref: nodejs/node#50222
PR-URL: nodejs/node#50252
Refs: nodejs/node#50222
Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
sercher added a commit to sercher/graaljs that referenced this issue Apr 25, 2024
Ref: nodejs/node#50222
PR-URL: nodejs/node#50252
Refs: nodejs/node#50222
Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
nodejs-github-bot pushed a commit that referenced this issue Jul 4, 2024
There was a commit that got merged that should have fixed the issue

ref: #50222 (comment)
PR-URL: #53692
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
aduh95 pushed a commit that referenced this issue Jul 12, 2024
There was a commit that got merged that should have fixed the issue

ref: #50222 (comment)
PR-URL: #53692
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
aduh95 pushed a commit that referenced this issue Jul 16, 2024
There was a commit that got merged that should have fixed the issue

ref: #50222 (comment)
PR-URL: #53692
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
marco-ippolito pushed a commit that referenced this issue Aug 19, 2024
There was a commit that got merged that should have fixed the issue

ref: #50222 (comment)
PR-URL: #53692
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
marco-ippolito pushed a commit that referenced this issue Aug 19, 2024
There was a commit that got merged that should have fixed the issue

ref: #50222 (comment)
PR-URL: #53692
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Luigi Pinca <[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. linux Issues and PRs related to the Linux platform. s390 Issues and PRs related to the s390 architecture.
Projects
None yet
Development

No branches or pull requests

2 participants