[v22.x] tools: disable failing coverage jobs #58770
Merged
+4
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Review requested:
|
aduh95
changed the title
nodejs-github-bot
added
meta
aduh95
force-pushed
the
skip-coverage-jobs
branch
from
ce08a5e to
27fc963
Compare
marco-ippolito
approved these changes
Jun 20, 2025
|
We probably should backport this to v20 |
richardlau
approved these changes
Jun 20, 2025
PR-URL: nodejs#58770 Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Richard Lau <[email protected]>
aduh95
force-pushed
the
skip-coverage-jobs
branch
from
27fc963 to
b7feda9
Compare
|
Landed in b7feda9 |
aduh95
added a commit
that referenced
this pull request
Jun 23, 2025
PR-URL: #58770 Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Richard Lau <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Those have been failing for a while, and no one has managed to find out how to fix it. Keeping a failing job that we ignore the result is really not healthy, and just wasteful at this point, let's disable it.