dotnet / dotnet/xharness

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

Open
#1,705 1 comment 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/33138599773

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

**Missing Data:**
- **Helix job identifier in Send to Helix log**: The required Send tests to Helix \(Unix\) log 723 for runtime build 1569716 contains no \`Sent Helix Job: <GUID>\` record, so the associated MacCatalyst xharness failure cannot be traversed from the mandated evidence source.
- *Alternatives*: Regenerate from a runtime build whose Helix submission log includes the job identifier, then rerun the observer.

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

**Last agent output:**
```
● Extract MacCatalyst Helix job (shell)
│ grep -oE 'Sent Helix Job: [a-f0-9-]+' /tmp/gh-aw/agent/helix-send-1569716-723.log
└ 1 line…
● missing_data (MCP: safeoutputs) · data_type: "Helix job identifier in Send to Helix log", reason:…
└ {"result":"success"}
Scan incomplete: the required runtime Helix submission log lacked its job identifier, so no xharness PR was created.
Changes +0 -0
Duration 1m 15s
Tokens ↑ 800.8k (754.9k cached, 45.9k written) • ↓ 4.1k (1.2k reasoning)
Resume copilot --resume=615b2663-5474-468a-af09-18667139c1df
```

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

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

> [!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/33138599773) · 29.3 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 4, 2026, 3:25 AM 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 33138599773, then read .github/skills/agentic-workflows/SKILL.md or the linked debug guide. Trace how the observer handles the missing Helix job identifier in the Send to Helix log. Done means the workflow failure is debugged and the observer can complete or report missing data appropriately.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.