-
Notifications
You must be signed in to change notification settings - Fork 30k
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: reduce impact of flaky HTTP server tests #42926
test: reduce impact of flaky HTTP server tests #42926
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Removed the file extensions, maybe that works. |
35014d7
to
06c1abe
Compare
Yep: node/test/parallel/parallel.status Lines 3 to 5 in 02e0c17
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The flakiness is also annoying on the GHA runner, and unfortunately this PR won't help with that I'm afraid. Oh well, at least it's improving things for the Jenkins CI, so LGTM.
@aduh95 I am not sure about that. #42741 (comment) suggested that GitHub Actions might respect the list of flaky tests. |
CI is failing because of nodejs/build#2917. |
CI is green but GitHub seems to be thinking that Jenkins is still running, and the commit queue refuses to run... |
Landed in 0fc455a |
Thank you @aduh95 :) |
This PR is dependent on #42846, so marking as blocked. |
Mark the tests as flaky on macOS and increase the timeout for other platforms (namely, FreeBSD).
Context: #42741 (comment)
Refs: #42741