Skip to content

[CI Failure Doctor] CI Failure Investigation - Run 36946 #17149

@github-actions

Description

@github-actions

🏥 CI Failure Investigation - Run #36946

Summary

  • The CI workflow run 36946 (commit 6d037e1) fails after the change Emit compilation error when agent file is imported with inlined-imports (#17140).
  • The test job reports golden mismatches in TestCodexEngineRenderMCPConfig because the expected MCP server container version (ghcr.io/github/github-mcp-server:v0.30.3) no longer matches the compiler output (v0.31.0).
  • The Integration: Workflow Misc Part 2 job aborts during go test ./pkg/workflow with exit code 1 while the failure report states “No individual test marked as failed,” so the actual panic/build issue is not visible in the truncated log.

Failure Details

  • Run: 22224416566
  • Commit: 6d037e1301dbe895fe190991180b94825f84d732
  • Trigger: push

Root Cause Analysis

  1. TestCodexEngineRenderMCPConfig (and related golden checks) still assert that the MCP server container is ghcr.io/github/github-mcp-server:v0.30.3, but the renderer now outputs v0.31.0, so the golden diff at codex_engine_test.go:373 fails on two lines where the container string is emitted.
  2. go test ./pkg/workflow exits with code 1 after TestNoWorkflowRunRepoSafetyForPushTrigger and friends, but the failure report says “No individual test marked as failed,” indicating a panic or build-time error occurred before a test could record its failure; the integration artifact (test-result-integration-Workflow Misc Part 2) is needed to identify the specific panic or compilation failure.

Failed Jobs and Errors

  • test: TestCodexEngineRenderMCPConfig expected container = "ghcr.io/github/github-mcp-server:v0.30.3" (line 13) and the JSON line 23 expected the same, but the actual output is v0.31.0.
  • Integration: Workflow Misc Part 2: go test for github.com/github/gh-aw/pkg/workflow terminates with FAIL github.com/github/gh-aw/pkg/workflow 4.781s and a subsequent summary saying “No individual test marked as failed,” so the underlying panic/build error must be extracted from the artifact before the cause can be fixed.

Investigation Findings

  • Running go test ./pkg/workflow -run TestCodexEngineRenderMCPConfig -count=1 locally is blocked because the Go toolchain download for go1.25.0 (requested by the repo) hits proxy.golang.org and returns 403 Forbidden inside this sandbox.
  • The integration job log ends with the package-level failure message but no stack trace, so reproducing the run or downloading the test-result-integration-Workflow Misc Part 2.zip artifact is necessary to capture the panic or compile error.

Recommended Actions

  • Update the golden expectations in codex_engine_test.go (and any other references) to match the new default MCP server container ghcr.io/github/github-mcp-server:v0.31.0 and rerun go test ./pkg/workflow ./pkg/workflow/....
  • Re-run Integration: Workflow Misc Part 2 (or inspect the test-result-integration-Workflow Misc Part 2.zip artifact) to capture the panic/build failure that causes go test to exit with code 1 despite reporting “No individual test marked as failed,” then fix that panic/compile error.

Prevention Strategies

  • When bumping the default MCP runtime/container version, update any golden fixtures or unit tests that assert the previous version so that version mismatches are caught earlier in go test failures.
  • Enhance integration failure logging (or the failure-report script) so that when the package exits with code 1 but no test is flagged, the panic or compile error is still preserved in the summary.

AI Team Self-Improvement

  • Before editing code that ships new default container versions, rerun the affected golden tests and update their expected strings (especially ghcr.io/github/github-mcp-server references) so AI agents do not rely on stale values.

Historical Context

  • This appears to be the first CI Failure Doctor issue for this particular signature; no earlier investigations reported the same container version mismatch or the mysterious package-level failure for pkg/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.

  • expires on Feb 21, 2026, 12:53 PM UTC

Metadata

Metadata

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