Skip to content

[CI Failure Doctor] CI Failure Investigation - Run #35868 #15934

@github-actions

Description

@github-actions

🏥 CI Failure Investigation - Run #35868

Summary

  • The pkg/workflow unit tests started failing while parsing sandbox configuration and building the activation job because the legacy sandbox.type field is no longer honored and the status-comment step only runs when StatusComment is explicitly true.
  • This blocks the test job from completing: sandbox-aware paths never enable AWF/SRT tooling and activation jobs skip the expected comment step even when ai-reaction is configured.

Failure Details

  • Run: 22037597263
  • Commit: 56007c18970fce9f8c5af0f6d20e79b46b890cad
  • Trigger: push (dependabot branch: dependabot/npm_and_yarn/actions/setup/js/types/node-25.2.3)

Root Cause Analysis

  1. The helper isSandboxEnabled() only inspects sandbox.agent and the firewall configuration. When a workflow uses the legacy sandbox.type field (sandbox: sandbox-runtime/sandbox-type) without an agent block, the helper returns false, making strict-mode validation, lock-for-agent, reaction job annotations, and plugin discovery believe the sandbox is disabled.
  2. buildActivationJob() only posts the “Add comment with workflow run link” step when StatusComment is non-nil. Workflows that only set ai-reaction relied on the default of status-comment=true, so the activation job now skips the comment step inside the job even though the expectation remains.

Failed Jobs and Errors

  • test job: https://github.com/github/gh-aw/actions/runs/22037597263/job/63673030591
    • compiler_jobs_test.go:495: Expected comment step in activation job from TestBuildActivationJobWithReaction
    • compiler_safe_outputs_test.go:968: Sandbox detection mismatch for TestCompilerIsSandboxEnabled/legacy_type_field_*
    • firewall_default_enablement_test.go:492: Expected no error when SRT is enabled... strict mode requires firewall to be enabled from TestStrictModeFirewallValidation/strict_mode_skips_validation_when_SRT_is_enabled
    • lock_for_agent_test.go:70: generated YAML no longer contains `GH_AW_LOCK_FOR_AGENT:

🩺 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 16, 2026, 3:03 PM 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