test(forge-test): #796 cache pinned binaries in a host store and copy them into the VM #799
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!799
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-796-host-binary-store"
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
The forge tests downloaded each pinned binary from upstream on every VM run, and codeberg serves the Forgejo binary at about 80 KB/s, so a run timed out. A new
madtea-dev forge-pins ensurecommand fetches every pinned binary once into a host store, verified by its SHA-256, and run-forge-tests.sh copies that store onto the VM's local disk before the run, so the suite is a cache hit and never downloads from the throttled source. Verified green: the forge suite runs in the VM off the store, with no upstream fetch.Closes #796