[CI Failure Doctor] CI Failure Investigation - Run #37203

[github-actions]

Summary

Wasm golden fixtures now compare for Copilot CLI 0.0.412 but the pipeline upgraded the CLI to 0.0.414, so the golden output no longer matches and the wasm-focused tests fail.

Failure Details

• Run: 22256493579 (https://github.com/github/gh-aw/actions/runs/22256493579)
• Commit: 1be6247
• Trigger: push

Root Cause Analysis

The wasm golden tests check the generated workflow snippets, which still expect install_copilot_cli.sh 0.0.412. After bumping the Copilot CLI binary to 0.0.414, the new output contains agent_version: "0.0.414" and the install step now runs install_copilot_cli.sh 0.0.414, so the tests flag the diff.

Failed Jobs and Errors

• test: TestWasmGolden_CompileFixtures/basic-copilot, TestWasmGolden_CompileFixtures/smoke-copilot, and TestWasmGolden_CompileFixtures/with-imports all failed because golden files still mention CLI 0.0.412.
• build-wasm: make test-wasm-golden exits with failure because the same wasm golden stretch fails.

Investigation Findings

• The failure report output recorded the mismatched CLI install step for each fixture and highlighted agent_version: "0.0.414" as the only difference.
• Regenerating the golden fixtures should update basic-copilot.md, smoke-copilot.md, and with-imports.md to expect the new CLI version and clear the failure.
• No other jobs in the workflow failed; everything after the wasm tests relies on them, so rerunning the pipeline should succeed after the fixtures are updated.

Recommended Actions

• Regenerate the wasm golden fixtures via make test-wasm-golden (or go test ./pkg/workflow -run TestWasmGolden_CompileFixtures -count=1) to capture install_copilot_cli.sh 0.0.414 and commit the updated basic-copilot.md, smoke-copilot.md, and with-imports.md.
• After committing the refreshed fixtures, rerun the workflow so test and build-wasm pass again.

Prevention Strategies

Document the need to rerun the wasm golden fixture generator whenever the Copilot CLI version is bumped so the tests stay in sync with the binary they install.

AI Team Self-Improvement

• Always regenerate wasm golden fixtures after updating the Copilot CLI binary version so the tests keep tracking the install command.
• When diagnosing wasm golden failures, compare the agent_version and install_copilot_cli.sh arguments against the golden files.

Historical Context

• Previous CI Failure Doctor investigations such as [CI Failure Doctor] CI Failure Investigation - Run #37172 are closed, and no open duplicate issue covers this CLI-version discrepancy.
• Search results for [CI Failure Doctor] with the cookie label returned only closed issues, so this run appears to be a new investigation.

🩺 Diagnosis provided by CI Failure Doctor

To install this workflow, run gh aw add githubnext/agentics/workflows/ci-doctor.md@ea350161ad5dcc9624cf510f134c6a9e39a6f94d. View source at https://github.com/githubnext/agentics/tree/ea350161ad5dcc9624cf510f134c6a9e39a6f94d/workflows/ci-doctor.md.

• expires on Feb 22, 2026, 12:14 PM UTC

[github-actions]

Run #37207 (https://github.com/github/gh-aw/actions/runs/22256701749) is failing for the same reason: the wasm golden fixtures still expect the Copilot CLI install step and agent_version fields to reference 0.0.412, but the pipeline now installs and reports 0.0.414 (/opt/gh-aw/actions/install_copilot_cli.sh 0.0.414 and agent_version: "0.0.414"). As a result, TestWasmGolden_CompileFixtures/basic-copilot, /smoke-copilot, and /with-imports all report output diffs and the test/build-wasm jobs exit with failure. Regenerating basic-copilot.md, smoke-copilot.md, and with-imports.md against CLI 0.0.414 should bring the golden fixtures back in sync and unblock the workflow.

🩺 Diagnosis provided by CI Failure Doctor

To install this workflow, run gh aw add githubnext/agentics/workflows/ci-doctor.md@ea350161ad5dcc9624cf510f134c6a9e39a6f94d. View source at https://github.com/githubnext/agentics/tree/ea350161ad5dcc9624cf510f134c6a9e39a6f94d/workflows/ci-doctor.md.

[github-actions]

This issue is being closed as outdated. A newer issue has been created: #17481

View newer issue

---

This action was performed automatically by the CI Failure Doctor workflow.