[aw] Smoke Bounded Queries gVisor is missing required data

Smoke Bounded Queries gVisor · issue · closed

Filter2mode:review mode:live
All recorded Export JSON
github-actions[bot]

published Jul 31, 2026, 7:40 PM · updated Jul 31, 2026, 8:38 PM

Workflow Failure

Workflow: Smoke Bounded Queries gVisor
Branch: fix-bounded-query-runtime-smokes
Run: https://github.com/github/gh-aw-firewall/actions/runs/30658601148

Warning

Missing Data Reported: The agent reported missing data during execution.

Missing Data:

  • bounded-query result for github/gh-aw go.mod check: The task requires the bounded query to return exactly `true`, but the query returned {"status":"error"}. Failure modes are indistinguishable by design, so root cause cannot be determined from this sandbox.
    • Context: Ran: bounded-query --repo github/gh-aw --schema '{"type":"boolean"}' with a script checking Path('/query/repo/go.mod').exists(), writing result via json.dumps to /query/out. Command took ~600s (consistent with the 10-minute timing bucket) and returned {"st
      [Content truncated due to length]
    • Alternatives: Retry the bounded-query invocation (budget permitting, up to 32 invocations/run) or verify the run's remaining information budget for github/gh-aw hasn't been exhausted.

Warning

Engine Failure: The copilot engine terminated unexpectedly.

Last agent output:

The bounded-query returned `{"status":"error"}` rather than `true`. Per the tool's design, all failure modes are indistinguishable, so I cannot determine the cause (script issue, budget, timeout, etc.). Reporting missing data as instructed.
● missing_data (MCP: safeoutputs) · data_type: "bounded-query result for github/gh-aw go.mod check"…
  └ {"result":"success"}
Reported via `missing_data`: the bounded-query smoke test ran successfully (fresh gVisor sandbox, ~600s latency matching the 10-minute timing bucket) but returned `{"status":"error"}` instead of `true`. Since all failure modes are indistinguishable by design, I could not determine whether this was a budget, timeout, or script issue — flagged for follow-up rather than reporting a false PASS.
Changes   +0 -0
Duration  11m 17s
Tokens    ↑ 333.6k • ↓ 1.5k • 256.4k (cached)
Run 'docker run --help' for more information
Run 'docker run --help' for more information
Run 'docker run --help' for more information

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-firewall/actions/runs/30658601148
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 Bounded Queries gVisor · 25.9 AIC ·

  • expires on Aug 7, 2026, 7:40 PM UTC