-
Notifications
You must be signed in to change notification settings - Fork 374
feat(cache): cache v2 in the agent #4237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 5 commits
a50ff2c
5265b8c
d51dc42
359d095
69eefd0
cbe3873
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| caches: | ||
| - name: gomodcache | ||
| # Module source (downloaded .go files, zips, go.mod) is | ||
| # platform-independent, so one key is shared across every os/arch. | ||
| cache_key: | ||
| - v2 | ||
| - { checksum: go.sum } | ||
| # ~-anchored: resolved against $HOME, independent of cwd | ||
| target_paths: | ||
| - ~/.gomodcache | ||
| - name: gocache | ||
| # Build cache holds compiled objects, which are platform-specific, so | ||
| # it stays keyed by os+arch. | ||
| cache_key: | ||
| - v2 | ||
| - { agent: os } | ||
| - { agent: arch } | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Non-blocking: This exact address never changes, and cache save explicitly skips an address that already exists. After the first successful Linux/AMD64 save,
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Still open —
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Still open — the
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Still open — the new platform writers do not change the fixed key, so once each platform’s first entry exists, later runs still cannot refresh it.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Still open — both
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Still open — both build-cache definitions retain fixed exact addresses, so existing entries still cannot be refreshed. |
||
| # ~-anchored: resolved against $HOME, independent of cwd | ||
| target_paths: | ||
| - ~/.gocache | ||
Uh oh!
There was an error while loading. Please reload this page.