ci: faster cargo check features #4429
Merged
Conversation
This file contains 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
Bumping up the size of the runner, since we added more compute-intensive logic back in [0]. The logic is still serialized, but now it should complete faster. I've noticed the cache getting evicted faster lately, due to multiple large PRs, so the extra compute will help offset the delay caused by cache busting. [0] f7234c0
conorsch
added
the
A-CI/CD
cratelyn
approved these changes
May 21, 2024
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.
Describe your changes
Bumping up the size of the runner, since we added more compute-intensive logic back in [0]. The logic is still serialized, but now it should complete faster. I've noticed the cache getting evicted faster lately, due to multiple large PRs, so the extra compute will help offset the delay caused by cache busting.
[0] f7234c0
Issue ticket number and link
Checklist before requesting a review
If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: