Repository navigation
ci(coverage): run tarpaulin with the llvm engine to fit the job budget - #227
Merged
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
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 full-suite checkpoint on 4cd1aff (run 37183925560) cancelled Coverage at its 45-minute timeout.
Cause: tarpaulin's default ptrace engine. The CI log shows about 30–37 s of overhead between one test binary finishing and the next one launching, regardless of how long the tests take. With ~75 binaries, that overhead alone is close to the whole budget. The oracle was simply the binary running when the clock ran out.
Fix:
make coveragenow passes--engine llvm(source-based instrumentation, no ptrace). No test binaries are excluded and the timeout is unchanged.Local measurement (32 cores, cargo-tarpaulin 0.37.5, same flags as
make coverage):The run averaged only 268% CPU because binaries run one after another, so the test phase should be roughly the same on the 4-vCPU runner. The build will take longer there. The next full-suite run will confirm the CI time.