[aw] Smoke Azure PI finished without a clear failure cause

已关闭
#69,529 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
1-2 天
新手友好度
22/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
azure, github-actions
领域
ci-cd

调研方向

Start with the linked run (actions/runs/38984821025) and open the logs for the failing Execute Pi CLI step in the agent job. The workflow definition is .github/workflows/smoke-azure-pi.md. The report gives no cause, so the first task is finding the error the driver exited on. Done means identifying the cause and either fixing the workflow or filing a clearer follow-up issue.

由索引模型根据 Issue 内容生成。

描述

agentic-workflows
Workflow Failure

Workflow: Smoke Azure PI
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/38984821025

[!WARNING]
Task Could Not Be Completed: The workflow recorded a report_incomplete signal: the task was not completed or completion could not be confirmed.

Error details:
Failure classification: unknown
Driver exit code: 1. The engine driver exited before a terminal safe output was recorded.
Last tool call status: not recorded
Failed tool calls observed: 0
Token budget state: unknown (no exhaustion signal recorded)
Step budget state (LLM invocations): unknown (no exhaustion signal recorded)
Safe-output tools: available at gateway snapshot (registered 5 tools)
Safe-output CLI calls observed: unknown (not recorded)
Safe-output MCP calls observed: 0
Safe-output persistence: not recorded
Agent finished without emitting a terminal safe output; task completion could not be confirmed.
Last engine error type: unknown
Retry attempts observed: 0

A comment or other safe output does not confirm that the requested task was completed. Only inferred runtime status and error codes are reported; agent text is excluded.

Failure Diagnostics

Agent job: agent
Agent job conclusion: failure
Failing step: Execute Pi CLI

The runtime did not record a specific cause. Check the linked run for failure details.

Only runtime metadata is shown; agent-generated text is excluded.

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/github/gh-aw/actions/runs/38984821025
Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

[!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:

safe-outputs:
  report-failure-as-issue: false

Generated from Smoke Azure PI · ◷

  • expires on Oct 17, 2026, 12:09 PM UTC
主要语言
Go
星标
5.5k
派生
606
平均合并
4 小时 47 分钟
30 天内合并 PR
797

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

github/gh-aw 的其他 Issue

查看 github/gh-aw 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。