[aw] Flaky Test Triage produced no safe outputs
- Dominant language
- C#
- Stars
- 5.5k
- Forks
- 1.5k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 141
Description
### Workflow Failure
**Workflow:** [Flaky Test Triage](https://github.com/dotnet/msbuild/blob/main/.github/workflows/flaky-test-detector.agent.md)
**Branch:** main
**Run:** https://github.com/dotnet/msbuild/actions/runs/34613382051
> [!WARNING]
> **No Safe Outputs Generated**: The agent job succeeded but did not produce any safe outputs.
This typically indicates:
- The safe output server failed to run
- The prompt failed to generate any meaningful result
- The agent should have called `noop` to explicitly indicate no action was taken
### 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/msbuild/actions/runs/34613382051
````
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 flaky-test-detector.agent failure in https://github.com/dotnet/msbuild/actions/runs/34613382051`
> [!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 [Flaky Test Triage](https://github.com/dotnet/msbuild/actions/runs/34613382051) · copilot · 10.7 AIC · [◷](https://github.com/search?q=repo%3Adotnet%2Fmsbuild+is%3Aissue+%22gh-aw-workflow-id%3A+flaky-test-detector.agent%22&type=issues)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with .github/workflows/flaky-test-detector.agent.md and the failed run linked in the issue. Read the gh-aw debug guidance or the agentic-workflows skill, then trace why the job produced no safe outputs. Done means the workflow handles this failure appropriately and no longer reports missing safe outputs for a successful agent job.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100