[aw] Smoke Claude: timed out

Cerrado
  • ¿Algo no está bien?
#11,018 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
20/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
github-actions
Área
ci-cd

Línea de trabajo

Start with the Smoke Claude workflow source, .github/workflows/smoke-claude.md, and its timeout-minutes frontmatter, then open the linked run #41497484290. The report classifies the failure as engine_outage with no terminal safe output, so the cause is not yet established. Done means the cause is identified and the workflow either completes or has a justified timeout change. Pull request #11005 is the related branch.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

agentic-workflows
What happened

Smoke Claude timed out.

View run #41497484290 · Workflow source · Previous failures

Branch: lpcox-fix-routed-run-false-failures

Pull Request: #11005

Next step

Review the failure details below for a targeted fix, or assign this issue to a coding agent to investigate.

Failure details

Agent Timed Out: The agent job exceeded the maximum allowed execution time (20 minutes).

To increase the timeout, add or update the timeout-minutes setting in your workflow's frontmatter:

---
timeout-minutes: 30
---
Runtime evidence

[!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: engine_outage
Driver exit code: 0
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 6 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.
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.

Optimize token consumption

This failure was triggered by a guardrail limit (max-turns / timeout). Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.) to analyze token usage and reduce costs:

Optimize the agentic workflow token consumption using https://raw.githubusercontent.com/github/gh-aw/main/optimize.md

The workflow run is at https://github.com/github/gh-aw-firewall/actions/runs/41497484290
Copy a debugging prompt

Paste this into your coding agent:

Debug the agentic workflow "smoke-claude" failure.
Follow https://raw.githubusercontent.com/github/gh-aw/main/debug.md
Failed run: https://github.com/github/gh-aw-firewall/actions/runs/41497484290

If the repository includes the agentic-workflows skill, load it before investigating.

Manage failure notifications

To stop creating failure issues for this workflow, set this in its frontmatter and recompile:

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

This only disables issue reporting; it does not fix the failure.

Generated from Smoke Claude · ◷

  • expires on Nov 9, 2026, 6:30 PM UTC
Lenguaje dominante
TypeScript
Estrellas
157
Forks
80
Merge medio
4 h 48 min
PR fusionados (30 d)
417

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/gh-aw-firewall

Todos los issues de github/gh-aw-firewall

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.