You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A screenshot is worth a thousand words. Currently test-core creates a Go module cache for each type of job - check, api, compile * [windows, linux, macos], api, package, where each one is nearly a gigabyte. I'm fairly sure we can reduce this all to 1 cache if we be smart and have the check job run first, and also have it do a a make bootstrap which accounts for a large chunk of the cache size.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
A screenshot is worth a thousand words. Currently
test-core
creates a Go module cache for each type of job -check
,api
,compile * [windows, linux, macos]
,api
,package
, where each one is nearly a gigabyte. I'm fairly sure we can reduce this all to 1 cache if we be smart and have thecheck
job run first, and also have it do a amake bootstrap
which accounts for a large chunk of the cache size.The text was updated successfully, but these errors were encountered: