Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.2k
test: mark test-worker-http2-stream-terminate flaky on Windows#43425
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
test: mark test-worker-http2-stream-terminate flaky on Windows #43425
Uh oh!
There was an error while loading. Please reload this page.
Conversation
The test is causing a lot of CI failures, so I'd say that we should mark this test flaky until someone comes up with a proper fix. Refs: nodejs#43084 Signed-off-by: Darshan Sen <[email protected]>
This comment was marked as outdated.
This comment was marked as outdated.
RaisinTen commented Jun 15, 2022
Hmm, the test still runs and fails on Windows: |
richardlau commented Jun 15, 2022
@RaisinTen AFAICT it worked and https://ci.nodejs.org/job/node-test-binary-windows-js-suites/15120/RUN_SUBSET=1,nodes=win2012r2-COMPILED_BY-vs2019-x86/ is yellow and not red. https://ci.nodejs.org/job/node-test-binary-windows-js-suites/15120/ failed because https://ci.nodejs.org/job/node-test-binary-windows-js-suites/15120/RUN_SUBSET=2,nodes=win2012r2-COMPILED_BY-vs2019-x86/ failed for a different test, test.parallel/test-worker-heap-snapshot. |
RaisinTen commented Jun 16, 2022
Ah, indeed! Thanks for the clarification @richardlau. :) |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
nodejs-github-bot commented Jun 17, 2022
nodejs-github-bot commented Jun 18, 2022
Landed in 61c7103 |
The test is causing a lot of CI failures, so I'd say that we should mark this test flaky until someone comes up with a proper fix. Refs: #43084 Signed-off-by: Darshan Sen <[email protected]> PR-URL: #43425 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
The test is causing a lot of CI failures, so I'd say that we should mark this test flaky until someone comes up with a proper fix. Refs: #43084 Signed-off-by: Darshan Sen <[email protected]> PR-URL: #43425 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
The test is causing a lot of CI failures, so I'd say that we should mark this test flaky until someone comes up with a proper fix. Refs: #43084 Signed-off-by: Darshan Sen <[email protected]> PR-URL: #43425 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
The test is causing a lot of CI failures, so I'd say that we should mark this test flaky until someone comes up with a proper fix. Refs: nodejs/node#43084 Signed-off-by: Darshan Sen <[email protected]> PR-URL: nodejs/node#43425 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
The test is causing a lot of CI failures, so I'd say that we should mark
this test flaky until someone comes up with a proper fix.
Refs: #43084
Signed-off-by: Darshan Sen [email protected]