docs(adr): 0052 keeps forge-test caches on VM-local disk #734
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!734
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-730-forge-cache-local-disk-doc"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
ADR 0052 point 3 now records where the forge-test caches live. The VM keeps the Go build cache, the Go module cache, and the resolved forge binary on local disk, not on the virtiofs persistent mount: a Go build and a running forge binary memory-map these files, and virtiofs rejects mmap (ENXIO), so a build on the mount fails at import. The persistent mount gives up warming these across runs, and each run re-fetches and rebuilds. The provisioning that sets GOCACHE, GOMODCACHE, and the binary-cache path, plus the confirming run, ride with #692.
Refs #730