-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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 tests as flaky as intermediate step #20835
Conversation
We have a few http2 issues that are currently resolved. Until they are, just mark these two tests as flaky.
509b793
to
236ffc0
Compare
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.
SGTM.
@addaleax this way the test itself does not have to be touched though and the code can be fixed. I personally believe that the status is somewhat meant for cases like the current one where in case we do not want a full revert. |
I prefer this since the tests will still fail instead of just being green but won't make the CI red. |
frequent CI failures due to flaky tests have been an issue off late - causes confusion to the PR at hand, needing to re-run leading to additional time and effort. Marking flaky until they are fixed is a good idea. |
@BridgeAR Feel free to land it, yes |
Landed in 8254e38 |
We have a few http2 issues that are currently resolved. Until they are, just mark these two tests as flaky. PR-URL: nodejs#20835 Reviewed-By: Anatoli Papirovski <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]>
We have a few http2 issues that are currently resolved. Until they are, just mark these two tests as flaky. PR-URL: #20835 Reviewed-By: Anatoli Papirovski <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]>
We have a few http2 issues that are currently resolved. Until they
are just mark these two tests as flaky.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes