[aw] Smoke Gemini: engine driver crashed
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- github-actions, typescript
Direzione di ricerca
Start with the linked workflow run and the .github/workflows/smoke-gemini.md workflow; follow the linked debug.md instructions to investigate the Gemini CLI failure, exit code 173, and failure signals. The issue gives no repository file or test for the underlying driver problem, so identify the relevant entry point from the run diagnostics. Done means finding and fixing the cause so the workflow completes successfully.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
What happened
Smoke Gemini engine driver crashed.
View run #40875537368 · Workflow source · Previous failures
Branch: main
Next step
Review the failure details below for a targeted fix, or assign this issue to a coding agent to investigate.
Failure details
Runtime evidence
[!WARNING]
Task Could Not Be Completed: The workflow recorded areport_incompletesignal: the task was not completed or completion could not be confirmed.
Error details:
Failure classification: driver_crash
Driver exit code: 173
Driver exit meaning: Unknown (engine-specific exit code)
Last driver stderr summary: not recorded (no classified stderr diagnostic)
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
The engine's final result reported an error; task completion could not be confirmed, even if safe outputs were recorded.
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 Gemini CLI
No additional engine error was captured. Check the reported failure signals and linked run for details.
Only runtime metadata is shown; agent-generated text is excluded.
Copy a debugging prompt
Paste this into your coding agent:
Debug the agentic workflow "smoke-gemini" failure.
Follow https://raw.githubusercontent.com/github/gh-aw/main/debug.md
Failed run: https://github.com/github/gh-aw-firewall/actions/runs/40875537368
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 Gemini · ◷
- expires on Nov 5, 2026, 1:02 PM UTC
- Lingua principale
- TypeScript
- Stelle
- 157
- Fork
- 80
- Merge medio
- 3h 45m
- PR unite (30g)
- 422
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di github/gh-aw-firewall
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
github/gh-aw-firewall#10778 ·
I maintainer di solito rispondono entro 1 giorno
-
agentic-workflows automated dependencies
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
github/gh-aw-firewall#3837 ·
I maintainer di solito rispondono entro 1 giorno
-
agentic-workflows
Difficoltà 3/5 1-2 giorni Idoneità per principianti 38/100
github/gh-aw-firewall#10812 ·
I maintainer di solito rispondono entro 1 giorno
-
agentic-workflows
Difficoltà 3/5 1-2 giorni Idoneità per principianti 38/100
github/gh-aw-firewall#10811 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
[awf] sandbox scope: detection job mounts input dir but detector cannot read it, reports greenApertaawf-triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
github/gh-aw-firewall#10809 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di github/gh-aw-firewall
Issue simili
-
b:minor bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
software-mansion/argent#1698 ·
I maintainer di solito rispondono entro 1 giorno
-
e2e-failure ready-to-code
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
redhat-developer/rhdh-plugin-export-overlays#4624 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
better-auth/better-auth#12132 · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
automation missing-model model-sync provider:tinfoil
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
anomalyco/models.dev#12053 ·
I maintainer di solito rispondono entro 1 giorno
-
o8 next debug build aborts on Glass to Dark appearance switch (nil identifier messaged before check)Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
hurttlocker/o8#5112 ·