Inspect runner-only aos-cli-tests failure on PR 838 #846

New issue

Closed

opened 2026-08-01 19:16:59 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-01 19:16:59 +00:00

Member

Evidence\n\n* PR: #838\n* Head: 3c82a902038e9d1c23b3178900de680f86553458\n* Failed workflow: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/2679\n* The aos-cli-tests task failed. The sibling ward-doctor and Python/pre-commit gate tasks passed.\n* ward exec aos-test and ward exec agent-terminal-test pass locally.\n* Both suites also pass from the PR checkout inside the exact published release image, digest sha256:8eb3b4a0fc1e724b5b9cfeef51e0b04efa166196b0d27a40028cf604e11001f8.\n* The same job-only failure appears in runs 2671, 2673, 2675, 2677, and 2679.\n* This Forgejo v15 instance returns 404 for the Forgejo v16 workflow/job log API. No authenticated browser surface was available in the engineer session.\n\n## Operator verification\n\n1. Open run 2679 and select the aos-cli-tests job.\n2. Capture the exact failed step, relevant error lines, and runner identity.\n3. If no workflow step began, inspect the assigned Forgejo Runner logs for task 22109 and record the setup failure.\n4. Return the evidence here. Do not rerun or dispatch the workflow merely as a probe.\n\n## Return condition\n\nThe evidence must distinguish a repository command failure from runner setup, network, or scheduling state. A repository-proven failure returns to Engineer. A runner or Forgejo failure stays with Ops.

## Evidence\n\n* PR: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/838\n* Head: 3c82a902038e9d1c23b3178900de680f86553458\n* Failed workflow: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/2679\n* The aos-cli-tests task failed. The sibling ward-doctor and Python/pre-commit gate tasks passed.\n* ward exec aos-test and ward exec agent-terminal-test pass locally.\n* Both suites also pass from the PR checkout inside the exact published release image, digest sha256:8eb3b4a0fc1e724b5b9cfeef51e0b04efa166196b0d27a40028cf604e11001f8.\n* The same job-only failure appears in runs 2671, 2673, 2675, 2677, and 2679.\n* This Forgejo v15 instance returns 404 for the Forgejo v16 workflow/job log API. No authenticated browser surface was available in the engineer session.\n\n## Operator verification\n\n1. Open run 2679 and select the aos-cli-tests job.\n2. Capture the exact failed step, relevant error lines, and runner identity.\n3. If no workflow step began, inspect the assigned Forgejo Runner logs for task 22109 and record the setup failure.\n4. Return the evidence here. Do not rerun or dispatch the workflow merely as a probe.\n\n## Return condition\n\nThe evidence must distinguish a repository command failure from runner setup, network, or scheduling state. A repository-proven failure returns to Engineer. A runner or Forgejo failure stays with Ops.

coilyco-ops added the

autonomy

live-collab

label

2026-08-01 19:16:59 +00:00

coilyco-ops referenced this issue from a commit

2026-08-01 19:32:23 +00:00

fix(ci): attach PR merge commit for Ward (closes #846)

coilyco-ops referenced this issue

2026-08-01 19:32:39 +00:00

fix(ci): admit detached PR checkouts to Ward #847

coilyco-ops removed the

autonomy

live-collab

label

2026-08-01 19:34:19 +00:00

coilyco-ops commented

2026-08-01 19:34:20 +00:00

Author

Member

Root cause confirmed as coilyco-flight-deck/ward#1632. Forgejo checks out pull-request merge results at detached HEAD, and the new aos-cli-tests job was the only CI job invoking Ward repository verbs directly.\n\nPR #847 preserves the synthetic merge commit, creates a temporary local branch with the pull request base as its upstream, and then runs the original Ward verbs unchanged.\n\nForgejo run 2687 passed. The aos-cli-tests, ward-doctor, and 606-test gate tasks are all green. The interactive operator handoff is no longer required.