chore: Test caching to speed up test action #1812
Merged
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.
Proposed Change
Trying to speed up CI after running into issues with the release and needing to wait on CI. Unfortunately the only real bottle neck is downloading dependencies, so for a single CI run there's not much that can be done. By default, the setup-go action will cache the root go.sum but with this change we're going to also cache nested go.sum files. With some rough testing I found this does speed up CI.
These are the results of some rough testing. In general I think caching the nested go.sum files does improve CI speed but it can definitely vary and this probably isn't definitive (such as windows tests taking longer with nested caching vs just the root).
Checklist