githubnext / githubnext/gh-aw-cao
[aw] CAO Evolution / Efficiency is missing required data
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
### Workflow Failure
**Workflow:** [CAO Evolution / Efficiency](https://github.com/githubnext/gh-aw-cao/blob/main/.github/workflows/cao-evolution-efficiency.md)
**Branch:** main
**Run:** https://github.com/githubnext/gh-aw-cao/actions/runs/35048733186
> [!WARNING]
> **Missing Data Reported**: The agent reported missing data during execution.
**Missing Data:**
- **cao-activity shared cache \(gh-aw-logs.sqlite / gh-aw-logs-shards/\*.jsonl\)**: The shared activity-cache restore did not populate $RUNNER\_TEMP/cao-activity for this run \(directory/file absent\), so schema-v2 run records for the required 7-day evidence window \(2026-09-09 to 2026-09-16 UTC\) with the prior 7-day comparison window were un
\[Content truncated due to length\]
- *Context*: Package-health snapshot required for githubnext/gh-aw-cao \(cao-evolution/efficiency worker, correlation\_id 35048301875-119\). Target repo has 40,000+ total Actions workflow runs across its full history \(per actions\_list list\_workflow\_runs total\_count\), so f
\[Content truncated due to length\]
- *Alternatives*: Checked target/.github/workflows/cao.json for package/worker mappings \(resolved successfully\) and searched SAFE\_OUTPUT\_REPO open issues for existing efficiency reports \(search\_issues found 0 matching open issues\). Sampled the most recent 100 Actions runs v
\[Content truncated due to length\]
### Action Required
**Assign this issue to an agent** to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
````
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/githubnext/gh-aw-cao/actions/runs/35048733186
````
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.
- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow cao-evolution-efficiency failure in https://github.com/githubnext/gh-aw-cao/actions/runs/35048733186`
> [!TIP]
>
> Stop reporting this workflow as a failure
>
> To stop a workflow from creating failure issues, set `report-failure-as-issue: false` in its frontmatter:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>
> Generated from [CAO Evolution / Efficiency](https://github.com/githubnext/gh-aw-cao/actions/runs/35048733186) · copilot · 50.4 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-id%3A+cao-evolution-efficiency%22&type=issues)
> - [x] expires on Sep 17, 2026, 2:47 AM UTC
Contributor guide
Research direction
Start with .github/workflows/cao-evolution-efficiency.md and the failed run linked in the issue. Read debug.md and .github/skills/agentic-workflows/SKILL.md, then inspect the missing shared cache and package-health data reported for the run. Done means the workflow obtains the required evidence data for its stated windows and completes without reporting missing data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100