chore(ci): optimize Windows go test with warm build cache strategy#507
Merged
chore(ci): optimize Windows go test with warm build cache strategy#507
Conversation
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
Instead of cleaning the entire build cache between batches (which forces recompilation of all shared dependencies each time), pre-build shared dependencies first, then only clean test-generated cache files between batches using timestamp-based filtering. This keeps the ~7.7G shared dependency cache warm while controlling peak disk usage at ~9.9G. Local benchmarks show this is ~5-6x faster compared to the previous cold-cache approach.
3aa9245 to
bf18ebb
Compare
hardfist
approved these changes
Mar 17, 2026
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
2 participants
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.
Summary
Optimize the Windows CI go test strategy. The previous approach ran tests in batches of 15 packages and cleaned the entire build cache (
go clean -cache) between batches, forcing recompilation of all shared dependencies (~7.7G) each time. This was very slow.The new approach:
go build ./internal/...) to warm the build cacheLocal benchmarks (macOS, 143 packages)
go clean -cache~5-6x faster while keeping peak disk usage under control (~9.9G vs 13G unbatched).
Related Links
N/A
Checklist