-
Notifications
You must be signed in to change notification settings - Fork 154
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
Rust cache tests #600
Rust cache tests #600
Conversation
@@ -2,7 +2,7 @@ name: benchmark_pr | |||
|
|||
on: | |||
pull_request: | |||
branches: [ '*' ] | |||
branches: [ 'asfd' ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@klaus993 change this
Triggered manually with clean cache to compare timings. With cached deps it took 15m to run. Without it it takes 21m. This is not currently caching the target directory, so it can improve a bit more. For that we'll need to make it build all targets so other workflows can benefit as well. PS: sorry @klaus993 for destroying the other PR, I misunderstood the "tests" in the title and thought it was for testing the cache action 🤦♂️ |
Codecov Report
@@ Coverage Diff @@
## main #600 +/- ##
=========================================
+ Coverage 0 94.83% +94.83%
=========================================
Files 0 60 +60
Lines 0 4144 +4144
=========================================
+ Hits 0 3930 +3930
- Misses 0 214 +214
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
2d04235
to
593a4aa
Compare
As explained in Swatinem/rust-cache#37, build artifacts only contribute to bloating the cache, as the divergences negate any benefits from caching them due to the cache key not changing over most commits.
No description provided.