dotnet / dotnet/xharness

[aw] Runtime Failure Observer (xharness) is missing required data

Open
#1,715 2 comments 0 reactions 0 assignees View on GitHub
agentic-workflows
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/33873110477

> [!WARNING]
> **Missing Data Reported**: The agent reported missing data during execution.

**Missing Data:**
- **Helix job identifier**: Build 1582322's identified failed Helix task submission log \(ID 487\) lacks either supported \`Sent Helix Job\` completion message, so no Helix work-item or console evidence can be retrieved.
- *Alternatives*: Regenerate the build or retain the Helix submission completion line, then rerun the observer.

> [!WARNING]
> **Engine Failure**: The `copilot` engine terminated unexpectedly.

**Last agent output:**
```
│ /tmp/gh-aw/agent/helix-send-1582322-487.log | grep -oE
│ '[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}'
└ 1 line…
● missing_data (MCP: safeoutputs) · data_type: "Helix job identifier", reason: "Build 1582322's ide…
└ {"result":"success"}
**Scan incomplete:** build `1582322`’s Helix submission log lacked a retrievable Helix job identifier, preventing required work-item and console analysis. No PR was created.
Changes +0 -0
Duration 2m 13s
Tokens ↑ 1.0m (990.0k cached, 37.4k written) • ↓ 3.3k (561 reasoning)
Resume copilot --resume=fe75650f-8bd1-4544-a396-1ac15c133303
```

### 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/33873110477
````

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/33873110477`

> [!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/33873110477) · 31.3 AIC · [◷](https://github.com/search?q=repo%3Adotnet%2Fxharness+is%3Aissue+%22gh-aw-workflow-id%3A+runtime-failure-observer.agent%22&type=issues)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with .github/workflows/runtime-failure-observer.agent.md and the failed run 33873110477. Investigate why the Build 1582322 Helix submission log lacks a retrievable job identifier or supported completion message. Done means the observer can retrieve the required Helix work-item and console evidence, or the workflow reports the failure appropriately.

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
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.