fix: recognize pessimistic coverage profile - #407
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 this PR does / why we need it
CI #406 allowed legacy branches to merge coverage without unsupported Compose coverage, but checked for
bvt-standalone.out. The standalone reusable workflow actually publishesbvt-pessimistic.out, so the coverage merge still rejected the valid legacy artifact set after every producer passed.Use the producer's actual profile filename.
Failure evidence: https://github.com/matrixorigin/matrixone/actions/runs/30253865089
Testing
git diff --checkmainand4.2-devmainstill rejects a single profile4.2-devaccepts only the singlebvt-pessimistic.outlegacy fallback