feat(testforge): #692 bring the forge-test VM standup into the repo #735
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!735
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-692-forge-vm-standup-in-repo"
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-test VM standup now lives in scripts/forge-vm/ (provision.sh, guest-setup.sh, isolation-smoke.sh) instead of outside the repo, so any machine with Incus can stand the VM up. The scripts carry no host internals: every host value is an env parameter with a portable default.
Caches move to VM-local disk (#730). guest-setup.sh leaves GOCACHE, GOMODCACHE, and the testforge binary cache at their per-user defaults under the home dir, and provision.sh no longer mounts a host cache. A Go build and a running forge binary memory-map these files and a virtiofs mount cannot mmap (ENXIO), so the caches have to be local; the matrix passes with local-disk caches.
The isolation smoke verifies the egress posture with no hardcoded addresses: a generic class baseline always runs, and a strong proof runs against real targets only when the caller passes them via env. ADR 0052 records the cache rule and the in-repo standup.
Refs #692