[cache-strategy] Daily Cache Strategy Analysis - 2026-08-27

[github-actions[bot]]

Daily Cache Strategy Analysis - 2026-08-27

Summary

Analyzed 76 workflow runs across 65 workflows where aw_info.json declared cache_memory: true.

No Critical or High findings met the issue-creation threshold today.

• No workflow source used a volatile cache key with ${{ github.run_id }} or ${{ github.run_number }} without restore-keys.
• prompt-clustering-analysis.md was checked as the main volatile-key candidate and is using the valid last-one-wins pattern with restore-keys at lines 39-43.
• cache-strategy cache memory was initialized and updated:
  • /tmp/gh-aw/cache-memory/cache-strategy/runs.json
  • /tmp/gh-aw/cache-memory/cache-strategy/index.json
  • /tmp/gh-aw/cache-memory/cache-strategy/known-issues.json

Strong Signals

Workflows with explicit cache-memory behavior in source and successful cache-update phases

These do not look misconfigured from today's evidence:

• Daily Go Test Parallelizer: 5 runs today, explicit cache instructions in source, update_cache_memory=success on runs 33032074515, 33046665669, 33069305330.
• Code Scanning Fixer: explicit reads/writes to /tmp/gh-aw/cache-memory/fixed-alerts.jsonl; one successful cache update on run 33032986061.
• Daily AW Cross-Repo Compile Check: explicit cache root /tmp/gh-aw/cache-memory/aw-compat and rolling history management in source.

Skipped cache updates on later failed runs appear to be downstream workflow failures, not cache-key misconfiguration.

Watchlist

Workflows worth re-checking tomorrow because the task prompt never moved beyond the generic cache-memory preamble

These runs had cache_memory: true in aw_info.json, but the rendered task prompt had no cache-memory references after the generic system section.

• Deep Report: runs 33031757597, 33057955120, 33090384370, 33117604491
  • Prompt evidence: only the generic <cache-memory> block at lines 19-23.
  • Source evidence: [.github/workflows/deep-report.md] uses repo-memory paths instead of /tmp/gh-aw/cache-memory/.
  • Interpretation: likely not a cache failure, but a metadata/tooling mismatch worth monitoring.
• Smoke workflows with the same pattern:
  • Smoke Copilot - AOAI (apikey) run 33030627298
  • Smoke Pi run 33030751053
  • Smoke Copilot ARM64 run 33030923389
  • Smoke Copilot run 33031095753
  • Smoke Gemini run 33031271487
  • Smoke Update Cross-Repo PR run 33031410425
  • Source evidence: these files declare cache-memory: true, but the task bodies do not include a cache-memory read/write step. Smoke Codex is the counterexample; it explicitly tests /tmp/gh-aw/cache-memory/smoke-codex-history.json.
  • Interpretation: these are low-confidence no-op cache declarations, not confirmed misses yet.

Recommended follow-up if the pattern repeats:

• Remove cache-memory: true where the workflow never reads or writes cache data.
• Or add a minimal explicit state file so future runs can prove cache benefit.
• Re-evaluate after at least 3 consecutive daily observations before opening workflow-specific issues.

Evidence

Representative evidence excerpts

• Valid volatile-key pattern, not flagged:

.github/workflows/prompt-clustering-analysis.md:39:  - key: prompt-clustering-cache-${{ github.run_id }}
.github/workflows/prompt-clustering-analysis.md:42:    restore-keys: |
.github/workflows/prompt-clustering-analysis.md:43:      prompt-clustering-cache-

• Explicit cache-memory usage example:

.github/workflows/daily-go-test-parallelizer.md:62: Read /tmp/gh-aw/cache-memory/go-test-parallelizer/state.json when it exists.
.github/workflows/daily-go-test-parallelizer.md:101: Always create /tmp/gh-aw/cache-memory/go-test-parallelizer/ and write state.json.

• Watchlist metadata/prompt mismatch example:

run 33031757597 (Deep Report): cache_memory=true, update_cache_memory=success, prompt_task_cache_mentions=0
run 33057955120 (Deep Report): cache_memory=true, update_cache_memory=success, prompt_task_cache_mentions=0
run 33090384370 (Deep Report): cache_memory=true, update_cache_memory=skipped, prompt_task_cache_mentions=0
run 33117604491 (Deep Report): cache_memory=true, update_cache_memory=skipped, prompt_task_cache_mentions=0

Actions Taken

• No GitHub issues created today.
• known-issues.json remains empty.
• Historical run data for today was saved for tomorrow's streak and miss-rate comparison.

Generated by 📊 Daily Cache Strategy Analyzer · codex · gpt54 · 146.6 AIC · ⌖ 10.8 AIC · ⊞ 13.2K · ◷

• expires on Aug 28, 2026, 2:01 PM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by Daily Cache Strategy Analyzer.

A newer discussion is available at Discussion #56720.