ci: match cobertura output of CodeCoverage 18.9 in coverage merge - #5
Merged
Merged
Conversation
|
peaceful-bot
approved these changes
Jul 17, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
Widens the coverage-merge glob to also match
TestResults/**/*.cobertura.xmlat the repo root, and drops the now-inaccurate "under tests/" wording from the zero-files error message.Why
Microsoft.Testing.Extensions.CodeCoverage18.9.0 changed where a relative--coverage-outputlands: 18.8.0 wrote<project>/bin/Release/net*/TestResults/, 18.9.0 anchors it to the platform results directory at the working directory root (TestResults/). Once the dependency bump arrives with the next promotion, the current glob matches zero files on a fresh CI clone and the merge step fails.The union keeps both layouts working:
maintoday (18.8.0) matches the old path, and the post-promotion tree (18.9.0) matches the new one —nullglobalready tolerates whichever side is empty. Verified by runningdotnet test --configuration Releaseagainst the bumped dependency set: exactly three cobertura files, all at repo-rootTestResults/.