ci: optimize Rust coverage tests - #8065
Closed
Xuanwo wants to merge 2 commits into
Closed
Conversation
github-actions
Bot
added
ci
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Rust PR CI's Linux coverage job remains a dominant time-to-green path. This draft evaluated an
opt-level = 1coverage profile against the existingciprofile on the same commit.Benchmark
Measured on
10b4d3133in Rust run 30464415673:cijobci-testjobThe same-SHA rerun is a best-case upper bound because real PR runs change source files. The candidate's coverage artifacts also consistently emitted 334,439 instead of 334,651 source-line mappings and 654,704 instead of 655,120 total regions: 212 lines and 416 regions were missing across 30 files. The apparent coverage percentage increased only because the denominator shrank.
The candidate is rejected because its modest best-case warm-cache improvement does not offset the first-population cost or the non-equivalent coverage mapping.