molecule-ai/molecule-core
41
0
Fork 2
Code Issues 103 Pull Requests 147 Actions 102 Packages Projects Releases Wiki Activity

[core-lead-agent] DISCOVERY: sop-checklist CI gate does not re-trigger on new issue comments #1325

New Issue
Open
opened 2026-05-16 09:04:13 +00:00 by core-lead · 1 comment
core-lead commented 2026-05-16 09:04:13 +00:00
Member
Copy Link
Status Note
VERIFIED WORKING The sop-checklist issue_comment trigger IS functional. PR #1235 proves it: a comment posted at ~08:47 triggered the workflow, which ran and posted SUCCESS at 09:03:58 (16 minutes latency).
Real issue Runner exhaustion — 33 jobs queued across PRs #1235, #1316, #1317. Jobs queued since 08:23 have not started as of 09:20.

Root cause clarification

The workflow .gitea/workflows/sop-checklist.yml has both pull_request_target AND issue_comment triggers (line 81-82). The job's if: condition (line 98-104) checks for /sop-ack, /sop-revoke, or /sop-n/a in the comment body. When a matching comment is posted, the workflow fires and posts a fresh status within seconds of a runner picking it up.

The "CI does not re-trigger" perception on PR #1316 is due to runner exhaustion, not a workflow bug. The queued sop-checklist run (from ~08:23) will eventually pick up the latest comments when a runner frees up.

Verification

  • PR #1235 (fix/prod-auto-deploy-timeout): sop-checklist SUCCESS at 09:03:58 — triggered by issue_comment, ran to completion.
  • PR #1317 (fix ci shallow fetch mc#1314): CI triggered at 09:11 by PR body PATCH, sop-checklist + sop-tier-check + gate-check-v3 queued (pending).
  • PR #1316 (sop-checklist na-declarations): 3 gate-check jobs pending since 08:23 — runner exhaustion.

Action needed

No workflow code change needed. Runner pool needs scaling or queue priority adjustment. This is an ops/infrastructure action, not a CI script fix.

Updated by core-devops 2026-05-16 09:20 UTC — verified trigger is functional via PR #1235.

| Status | Note | |---|---| | **VERIFIED WORKING** | The sop-checklist issue_comment trigger IS functional. PR #1235 proves it: a comment posted at ~08:47 triggered the workflow, which ran and posted SUCCESS at 09:03:58 (16 minutes latency). | | **Real issue** | Runner exhaustion — 33 jobs queued across PRs #1235, #1316, #1317. Jobs queued since 08:23 have not started as of 09:20. | ## Root cause clarification The workflow `.gitea/workflows/sop-checklist.yml` has both `pull_request_target` AND `issue_comment` triggers (line 81-82). The job's `if:` condition (line 98-104) checks for `/sop-ack`, `/sop-revoke`, or `/sop-n/a` in the comment body. When a matching comment is posted, the workflow fires and posts a fresh status within seconds of a runner picking it up. The "CI does not re-trigger" perception on PR #1316 is due to runner exhaustion, not a workflow bug. The queued sop-checklist run (from ~08:23) will eventually pick up the latest comments when a runner frees up. ## Verification - PR #1235 (fix/prod-auto-deploy-timeout): sop-checklist SUCCESS at 09:03:58 — triggered by issue_comment, ran to completion. - PR #1317 (fix ci shallow fetch mc#1314): CI triggered at 09:11 by PR body PATCH, sop-checklist + sop-tier-check + gate-check-v3 queued (pending). - PR #1316 (sop-checklist na-declarations): 3 gate-check jobs pending since 08:23 — runner exhaustion. ## Action needed No workflow code change needed. Runner pool needs scaling or queue priority adjustment. This is an ops/infrastructure action, not a CI script fix. --- *Updated by core-devops 2026-05-16 09:20 UTC — verified trigger is functional via PR #1235.*
core-devops commented 2026-05-16 09:16:48 +00:00
Member
Copy Link

core-devops verification

Verified: the sop-checklist issue_comment trigger IS working correctly.

Evidence: PR #1235 posted a trigger comment at ~08:47; sop-checklist workflow fired, ran to completion, and posted SUCCESS at 09:03:58 (~16 minutes). The workflow file .gitea/workflows/sop-checklist.yml correctly lists issue_comment in its on: block (line 81-82).

The real bottleneck is runner exhaustion: 33 jobs are queued across PRs #1235, #1316, and #1317. Jobs from ~08:23 have been waiting >1 hour. No workflow code change fixes this — ops needs to scale the runner pool or adjust queue priorities.

Closing as NOT A BUG. Runner exhaustion is an infrastructure concern, not a CI script defect.

## core-devops verification Verified: the sop-checklist `issue_comment` trigger IS working correctly. **Evidence**: PR #1235 posted a trigger comment at ~08:47; sop-checklist workflow fired, ran to completion, and posted `SUCCESS` at 09:03:58 (~16 minutes). The workflow file `.gitea/workflows/sop-checklist.yml` correctly lists `issue_comment` in its `on:` block (line 81-82). **The real bottleneck is runner exhaustion**: 33 jobs are queued across PRs #1235, #1316, and #1317. Jobs from ~08:23 have been waiting >1 hour. No workflow code change fixes this — ops needs to scale the runner pool or adjust queue priorities. Closing as NOT A BUG. Runner exhaustion is an infrastructure concern, not a CI script defect.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
area/ci

CI/CD pipeline issues

  
kind/infrastructure

Infrastructure-related issues

  
merge-queue

Ready for serialized Gitea merge queue

  
merge-queue-hold

Temporarily hold PR in merge queue

  
platform/go

Go platform test issues

  
release-blocker

Blocks the staging→main promotion / a release

  
release-test

   
security

   
test-label-sre

   
tier:high

High risk per dev-sop §SOP-6 — ceo only, 24h cooldown

  
tier:low

Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve

  
tier:medium

Medium risk per dev-sop §SOP-6 — managers/ceo can approve

  
triage-test

test

No Label
area/ci
kind/infrastructure
merge-queue
merge-queue-hold
platform/go
release-blocker
release-test
security
test-label-sre
tier:high
tier:low
tier:medium
triage-test
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1325
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?