Conversation
… of downloading releases
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.
The Linux job spent 98s compiling cargo-dylint and dylint-link and most of cargo test's 87s building the driver. The two binaries are now built once per dylint version and cached (nothing prebuilt is downloaded), target/ and ~/.dylint_drivers are cached, and the cargo build that cargo test repeats is gone. macOS gets the same caches but only runs on the weekly cron; the lints are not platform specific and those runners are slower.
This PR's run pays the one-off cost; the next push shows the cached time. If a branch rule pins the old job name, it is now linux.