-
Notifications
You must be signed in to change notification settings - Fork 18
ci: remove cargo clean step from coverage report job #1541
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: remove cargo clean step from coverage report job #1541
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1541 +/- ##
==========================================
- Coverage 71.78% 71.75% -0.03%
==========================================
Files 426 426
Lines 70114 70114
==========================================
- Hits 50332 50313 -19
- Misses 19782 19801 +19
🚀 New features to boost your workflow:
|
BenchmarksComparisonBenchmark execution time: 2026-02-10 01:54:44 Comparing candidate commit a15ee92 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 57 metrics, 2 unstable metrics. CandidateCandidate benchmark detailsGroup 1
Group 2
Group 3
Group 4
Group 5
Group 6
Group 7
Group 8
Group 9
Group 10
Group 11
Group 12
Group 13
Group 14
Group 15
Group 16
Group 17
Group 18
Group 19
BaselineOmitted due to size. |
Artifact Size Benchmark Reportaarch64-alpine-linux-musl
aarch64-unknown-linux-gnu
libdatadog-x64-windows
libdatadog-x86-windows
x86_64-alpine-linux-musl
x86_64-unknown-linux-gnu
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
The coverage report job is doing a cargo clean before it uploads results. That takes time, and also results in the target folder in the cache being empty when it gets uploaded. Now that we're using larger runners for the coverage job and we are aggressively freeing up space I don't think it's still necessary.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.