Investigate uncached cmd/ward suite flake during PR verification #1634

New issue

Closed

opened 2026-08-01 20:21:01 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-01 20:21:01 +00:00

Member

Sighting

While verifying the corrective test-only change for ward#1632, the first fully uncached run failed in the command package:

Command: GOCACHE=<fresh-task-cache> ward --audit-override-dirty exec test
Result: github.com/coilyco-flight-deck/ward/cmd/ward failed after 46.329s, causing the full target to exit 2.
The individual test name scrolled outside the retained tool output before the package summary, so this report preserves that evidence gap rather than inventing a name.

Without any code change between runs, a second full uncached run used GOFLAGS="-json -count=1" ward --audit-override-dirty exec test and passed with no Action=fail record and exit 0.

Candidate causes

Shared process environment or temporary Git fixture state in cmd/ward tests.
A first-build or fresh-Go-cache interaction that cached local runs normally hide.
Timing-sensitive command-package test behavior under the full package suite.

Acceptance

Reproduce with failure-only JSON retained from the start.
Identify the individual nondeterministic test.
Make the fixture hermetic and prove repeated uncached command-package runs.

Related verification: ward#1632 and PR #1633.

## Sighting While verifying the corrective test-only change for ward#1632, the first fully uncached run failed in the command package: * Command: `GOCACHE=<fresh-task-cache> ward --audit-override-dirty exec test` * Result: `github.com/coilyco-flight-deck/ward/cmd/ward` failed after 46.329s, causing the full target to exit 2. * The individual test name scrolled outside the retained tool output before the package summary, so this report preserves that evidence gap rather than inventing a name. Without any code change between runs, a second full uncached run used `GOFLAGS="-json -count=1" ward --audit-override-dirty exec test` and passed with no `Action=fail` record and exit 0. ## Candidate causes * Shared process environment or temporary Git fixture state in `cmd/ward` tests. * A first-build or fresh-Go-cache interaction that cached local runs normally hide. * Timing-sensitive command-package test behavior under the full package suite. ## Acceptance * Reproduce with failure-only JSON retained from the start. * Identify the individual nondeterministic test. * Make the fixture hermetic and prove repeated uncached command-package runs. Related verification: ward#1632 and PR #1633.

coilyco-ops referenced this issue

2026-08-05 09:54:40 +00:00

Isolate detached broker goroutines in cmd/ward tests #1630

coilyco-ops commented

2026-08-05 09:54:50 +00:00

Author

Member

Decision resolved by Kai on 2026-08-05.

Closing as duplicate evidence for #1630. The one uncached failure and the evidence gap are preserved on #1630, whose acceptance now requires repeated fresh-cache cmd/ward runs with failure-only JSON retained from the beginning.

If #1630 lands and a later fresh-cache run captures a distinct failing test, file that named failure as a new focused issue.

Decision resolved by Kai on 2026-08-05. Closing as duplicate evidence for #1630. The one uncached failure and the evidence gap are preserved on #1630, whose acceptance now requires repeated fresh-cache cmd/ward runs with failure-only JSON retained from the beginning. If #1630 lands and a later fresh-cache run captures a distinct failing test, file that named failure as a new focused issue.

coilyco-ops closed this issue

2026-08-05 09:54:57 +00:00

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-flight-deck/ward#1634

No description provided.

Rows
Columns