bug(forge-test): the adr live forge test fails under the push-model runner, which ships no .git #795

Closed
opened 2026-10-17 16:48:15 +00:00 by hexajon · 0 comments
Owner

What happens

scripts/forge-vm/run-forge-tests.sh pushes the committed tree into the VM with git archive HEAD, which ships tracked files only and no .git. The adr live forge test then has no checkout with an origin to resolve.

Running the forge-tagged suite over internal/service/adr fails:

--- FAIL: TestDecisionIssues_ForgeURL_Live (8.68s)
    adr_forge_test.go:147: Check: cannot resolve the repository for issue tracking (pass --skip-remote-issues to skip): no forge repository detected for this checkout

The runner also warns the pushed tree has no git identity (user.name "" in git vs "forgetest" in the forge).

Why it matters

The live forge test is the acceptance proof for the cross-forge decision-issue link (#632) and the file-reference check (#658). Both landed on main, but their live-forge acceptance cannot run green through the committed runner, so neither closes on a real forge run.

Possible directions

  • The test sets up its own checkout wired to the throwaway forge, so it does not need a .git in the pushed tree.
  • Or the runner ships a real checkout for the packages that need an origin, without a host mount.

Relates to #677, #678, #693.

## What happens scripts/forge-vm/run-forge-tests.sh pushes the committed tree into the VM with `git archive HEAD`, which ships tracked files only and no `.git`. The adr live forge test then has no checkout with an origin to resolve. Running the forge-tagged suite over internal/service/adr fails: --- FAIL: TestDecisionIssues_ForgeURL_Live (8.68s) adr_forge_test.go:147: Check: cannot resolve the repository for issue tracking (pass --skip-remote-issues to skip): no forge repository detected for this checkout The runner also warns the pushed tree has no git identity (user.name "" in git vs "forgetest" in the forge). ## Why it matters The live forge test is the acceptance proof for the cross-forge decision-issue link (#632) and the file-reference check (#658). Both landed on main, but their live-forge acceptance cannot run green through the committed runner, so neither closes on a real forge run. ## Possible directions - The test sets up its own checkout wired to the throwaway forge, so it does not need a .git in the pushed tree. - Or the runner ships a real checkout for the packages that need an origin, without a host mount. Relates to #677, #678, #693.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
sixfold-space/madtea#795
No description provided.