ci: disable broken code coverage on windows #6687
Merged
Conversation
This file contains 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
|
As a casual contributor, I second this move. First, it is frustrating to not get a green checkmark on a correct PR. Second, getting a red mark and seeing this test fail requires investigating to determine whether the PR code is to blame or not. |
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.
The
Code Coverage (windows-latest, windows, nightly-x86_64-pc-windows-gnu)CI step seems to always fail for all PRs, and has been broken for several months now: #6534.Instead of wasting even more CPU time (and perhaps money?) on a broken CI step that apparently noone wants to fix it, let's just deactivate it for now. If someone wants to fix it later, a FIXME points at the open issue #6686, which also serves as a good place to discuss potential fixes, should someone ever be interested.