eco/factorio --help tests fail on main with exit status 1 from go run subprocess #136

Open
opened 2026-05-28 07:28:28 +00:00 by coilysiren · 0 comments
Owner

Symptom Three help-output tests fail on main (go test ./cmd/coily/):

  • TestEcoWorld_HelpListsAllSubVerbs - eco world --help failed: exit status 1
  • TestFactorioMods_HelpListsListAndSync - factorio mods --help failed: exit status 1
  • TestFactorioMods_SyncHelpListsFlags - factorio mods sync --help failed: exit status 1

Each test shells out via go run ./cmd/coily gaming eco world --help (and the factorio equivalents) and asserts the subprocess exits 0; it exits 1 instead.

Pre-existing Reproduced on clean main (commit a955d66) with no local changes - confirmed by stashing an unrelated go.mod bump and re-running. Not a regression from the cli-guard v0.1.0 bump.

Not yet root-caused Could not reproduce the subprocess directly from this host because go run is denied by the coily lockdown. The go run invocation inside the test binary is unaffected by the hook, so the exit-1 comes from coily itself (or its build under the test's invocation), not from the lockdown.

Surfaced while bumping coily to cli-guard v0.1.0 to ship the lockdown trailing-newline fix (#135).

**Symptom** Three help-output tests fail on `main` (`go test ./cmd/coily/`): - `TestEcoWorld_HelpListsAllSubVerbs` - `eco world --help failed: exit status 1` - `TestFactorioMods_HelpListsListAndSync` - `factorio mods --help failed: exit status 1` - `TestFactorioMods_SyncHelpListsFlags` - `factorio mods sync --help failed: exit status 1` Each test shells out via `go run ./cmd/coily gaming eco world --help` (and the factorio equivalents) and asserts the subprocess exits 0; it exits 1 instead. **Pre-existing** Reproduced on clean `main` (commit a955d66) with no local changes - confirmed by stashing an unrelated go.mod bump and re-running. Not a regression from the cli-guard v0.1.0 bump. **Not yet root-caused** Could not reproduce the subprocess directly from this host because `go run` is denied by the coily lockdown. The `go run` invocation inside the test binary is unaffected by the hook, so the exit-1 comes from coily itself (or its build under the test's invocation), not from the lockdown. Surfaced while bumping coily to cli-guard v0.1.0 to ship the lockdown trailing-newline fix (#135).
coilysiren added
P2
and removed
P1
labels 2026-05-31 06:59:41 +00:00
Sign in to join this conversation.
No labels
P0
P1
P2
P3
P4
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.

Dependencies

No dependencies set.

Reference
coilyco-bridge/coily#136
No description provided.