-
Notifications
You must be signed in to change notification settings - Fork 189
Closed as not planned
Labels
cookieIssue Monster Loves Cookies!Issue Monster Loves Cookies!
Description
🏥 CI Failure Investigation - Run #35868
Summary
- The
pkg/workflowunit tests started failing while parsing sandbox configuration and building the activation job because the legacysandbox.typefield is no longer honored and the status-comment step only runs whenStatusCommentis explicitly true. - This blocks the
testjob from completing: sandbox-aware paths never enable AWF/SRT tooling and activation jobs skip the expected comment step even whenai-reactionis 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
- The helper
isSandboxEnabled()only inspectssandbox.agentand the firewall configuration. When a workflow uses the legacysandbox.typefield (sandbox: sandbox-runtime/sandbox-type) without anagentblock, the helper returnsfalse, making strict-mode validation, lock-for-agent, reaction job annotations, and plugin discovery believe the sandbox is disabled. buildActivationJob()only posts the “Add comment with workflow run link” step whenStatusCommentis non-nil. Workflows that only setai-reactionrelied on the default ofstatus-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 jobfromTestBuildActivationJobWithReactioncompiler_safe_outputs_test.go:968:Sandbox detection mismatchforTestCompilerIsSandboxEnabled/legacy_type_field_*firewall_default_enablement_test.go:492:Expected no error when SRT is enabled... strict mode requires firewall to be enabledfromTestStrictModeFirewallValidation/strict_mode_skips_validation_when_SRT_is_enabledlock_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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
cookieIssue Monster Loves Cookies!Issue Monster Loves Cookies!