gate: run the forge tests only inside an Incus VM #692
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.
Blocks
Depends on
#674 epic: run forge tests against throwaway Forgejo and Gitea servers behind a real proxy
sixfold-space/madtea
#730 forge-test gate: keep GOCACHE off the virtiofs cache mount (Go mmap fails)
sixfold-space/madtea
Reference
sixfold-space/madtea#692
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
What
The forge tests start real Forgejo, Gitea, and Traefik binaries. In the local
gate, these binaries run only inside an Incus VM, never directly on a
developer's OS. The VM can run on the developer's machine or on another machine
that the gate can reach. Today
scripts/gate.shrunsgo testdirectly on thedeveloper's OS, so the harness would start the binaries there.
What to build
scripts/gate.shto run theforge tests inside it, on the developer's machine or on another machine.
go testruns as a normal user, because Forgejo and Gitearefuse to start as root.
Acceptance
developer's OS.
forges, with no skipped forge test.
machine.
Part of #674. #678 needs this.
hexajon referenced this issue2026-10-03 18:04:29 +00:00