Skip to content

[CI Failure Doctor] CI Failure Investigation - Run #37641 #18061

@github-actions

Description

@github-actions

Summary

The test failure and build-wasm jobs failed because the wasm golden fixtures still expected Copilot CLI version 0.0.414 while the workflows now install 0.0.415. The test harness reports generated output diffs for the with-imports, basic-copilot, and smoke-copilot fixtures.

Failure Details

Root Cause Analysis

constants.DefaultCopilotVersion had already been bumped to 0.0.415, which causes every wasm golden workflow to emit agent_version: "0.0.415" and an install_copilot_cli.sh 0.0.415 step. The golden files and documentation in pkg/workflow/testdata/wasm_golden/TestWasmGolden_CompileFixtures (and the associated .changeset/scratchpad notes) were still pinned to 0.0.414, so the golden test asserts fail immediately after the version bump.

Failed Jobs and Errors

  • test failure job (TestWasmGolden_CompileFixtures): golden diff reports agent_version and install step referencing 0.0.415 instead of the expected 0.0.414 for with-imports, basic-copilot, and smoke-copilot fixtures.
  • build-wasm job (make test-wasm-golden): TestWasmGolden_NativeVsStringAPI logs native vs string API output differs for the same fixtures due to the version change; the job ultimately fails with FAIL github.com/github/gh-aw/pkg/workflow from the same golden mismatch.
Investigation Findings
  • Failure surfaced every time the wasm golden tests run because the runtime was already installing Copilot CLI 0.0.415, so the fixtures were updated structurally (agent_version, install steps) despite the golden files still locking 0.0.414.
  • Attempted to exercise go test ./pkg/workflow -run TestWasmGolden_CompileFixtures locally, but the build requires Go 1.25 and the toolchain download from golang.org/toolchain is blocked (Forbidden). Setting GOTOOLCHAIN=local runs Go 1.24.12, but go.mod demands go >= 1.25, so the test cannot be executed in this environment.

Recommended Actions

  • Update the wasm golden fixtures plus .changeset/scratchpad references so they expect Copilot CLI 0.0.415. (Done in this investigation.)
  • Re-run the test failure and build-wasm jobs after the version bump to verify the golden tests pass once the CI runner can reach the required Go toolchain.

Prevention Strategies

When bumping the default Copilot CLI version, regenerate the wasm golden fixtures and update any docs or changelog entries that snapshot the CLI version. Running make test-wasm-golden immediately after the bump catches these mismatched outputs before CI runs.

AI Team Self-Improvement

  • After adjusting default versions for AI runtimes/installers, regenerate any golden fixtures/testdata that embed those versions.
  • Run make test-wasm-golden (or the relevant golden test suite) as part of the version bump workflow so CI does not fail due to stale fixtures.
Historical Context No prior `[CI Failure Doctor]` issues surfaced by this investigation that match this signature.

🩺 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 25, 2026, 5:05 AM UTC

Metadata

Metadata

Assignees

No one assigned

    Labels

    cookieIssue Monster Loves Cookies!

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions