Cache Strategy Problem: Daily Go Test Parallelizer
Severity: 🟠 High
Workflow: Daily Go Test Parallelizer
Analysis Date: 2026-08-28
Issue Type: Misconfigured cache
Problem Description
The workflow declares cache-memory: true and the prompt explicitly requires it to round-robin through test files using /tmp/gh-aw/cache-memory/go-test-parallelizer/state.json. After 9 observed runs across 2026-08-27 and 2026-08-28, that state file is still absent, which means the workflow is not persisting its position and is effectively cold-starting every time.
Evidence
- Miss streak: 2 consecutive analyzed days
- Miss rate (14d): 100%
- Last cache hit: never
- Observed runs: 9
- Rebuild excess tokens (14d): 1,030,663
- Log signals: Prompt says
Read /tmp/gh-aw/cache-memory/go-test-parallelizer/state.json when it exists and Always create /tmp/gh-aw/cache-memory/go-test-parallelizer/ and write the last path ... to state.json, but /tmp/gh-aw/cache-memory/go-test-parallelizer/state.json is missing after the runs.
Recommended Fix
- Persist the state file on every successful agent completion so
state.json survives to the next run.
- Add a post-write existence check before the cache-memory commit/upload steps to fail fast when the expected file is missing.
- Confirm the next run reads the prior value instead of reinitializing from the first test path when the file should already exist.
Expected Impact
If fixed, this workflow should stop reprocessing the same leading test files and materially reduce wasted agent work across its frequent daily runs.
Detected by the Daily Cache Strategy Analyzer
Generated by 📊 Daily Cache Strategy Analyzer · codex · gpt54 · 164.1 AIC · ⌖ 7.9 AIC · ⊞ 13.2K · ◷
Cache Strategy Problem: Daily Go Test Parallelizer
Severity: 🟠 High
Workflow:
Daily Go Test ParallelizerAnalysis Date: 2026-08-28
Issue Type: Misconfigured cache
Problem Description
The workflow declares
cache-memory: trueand the prompt explicitly requires it to round-robin through test files using/tmp/gh-aw/cache-memory/go-test-parallelizer/state.json. After 9 observed runs across 2026-08-27 and 2026-08-28, that state file is still absent, which means the workflow is not persisting its position and is effectively cold-starting every time.Evidence
Read /tmp/gh-aw/cache-memory/go-test-parallelizer/state.json when it existsandAlways create /tmp/gh-aw/cache-memory/go-test-parallelizer/ and write the last path ... to state.json, but/tmp/gh-aw/cache-memory/go-test-parallelizer/state.jsonis missing after the runs.Recommended Fix
state.jsonsurvives to the next run.Expected Impact
If fixed, this workflow should stop reprocessing the same leading test files and materially reduce wasted agent work across its frequent daily runs.
Detected by the Daily Cache Strategy Analyzer