[aw] Runtime Failure Observer (xharness) is missing required data
- Dominant language
- C#
- Stars
- 189
- Forks
- 67
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 29
Description
### Workflow Failure
**Workflow:** [Runtime Failure Observer (xharness)](https://github.com/dotnet/xharness/blob/main/.github/workflows/runtime-failure-observer.agent.md)
**Branch:** main
**Run:** https://github.com/dotnet/xharness/actions/runs/33392187903
> [!WARNING]
> **Missing Data Reported**: The agent reported missing data during execution.
**Missing Data:**
- **Helix console log**: The required console request for failing work item System.Diagnostics.Tools.Tests in Helix job c751ae0a-9c9c-4ae7-b20e-f7e9cec01cd0 returned HTTP 404, so xharness evidence cannot be assessed.
- *Alternatives*: Rerun the observer against a build whose Helix console remains available.
> [!WARNING]
> **Engine Failure**: The `copilot` engine terminated unexpectedly.
**Last agent output:**
```
│ work item System.Diagnostics.Tools.Tests in Helix job c751ae0a-9c9c-4ae7-b20e-f7e9cec01cd0
│ returned HTTP 404, so xharness evidence cannot be assessed.","alternatives":"Rerun the observer
│ against a build whose Helix console remains available.","integrity":"high","secrecy":"public"}'
│ | safeoutputs missing_data .
└ 14 lines…
**Analysis incomplete.** A required Helix console log returned HTTP 404 for a failing work item, preventing reliable xharness diagnosis.
Changes +0 -0
Duration 1m 50s
Tokens ↑ 999.7k (947.2k cached, 52.4k written) • ↓ 4.4k (732 reasoning)
Resume copilot --resume=9e926ac2-f696-4651-a652-59359003a891
```
### 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/dotnet/xharness/actions/runs/33392187903
````
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 runtime-failure-observer.agent failure in https://github.com/dotnet/xharness/actions/runs/33392187903`
> [!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 [Runtime Failure Observer (xharness)](https://github.com/dotnet/xharness/actions/runs/33392187903) · 34.8 AIC · [◷](https://github.com/search?q=repo%3Adotnet%2Fxharness+is%3Aissue+%22gh-aw-workflow-id%3A+runtime-failure-observer.agent%22&type=issues)
> - [x] expires on Sep 7, 2026, 12:38 PM UTC
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with .github/workflows/runtime-failure-observer.agent.md and the failed run linked in the issue, then read the agentic-workflows guidance in .github/skills/agentic-workflows/SKILL.md. Investigate why the Helix console request returns HTTP 404 and rerun the observer against an available build to confirm that the required evidence can be assessed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100