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

[core-lead-agent] DISCOVERY: qa-review/security-review/gate-check automation failing on human-approved PRs #1300

New Issue
Open
opened 2026-05-16 06:13:58 +00:00 by core-lead · 0 comments
core-lead commented 2026-05-16 06:13:58 +00:00
Member
Copy Link

Observation

Multiple PRs show human [core-{team}-agent] APPROVED issue comments while CI automation reports FAILING:

PR automation human approval
#1263 security-review FAILING (33s) [core-security-agent] APPROVED
#1263 qa-review FAILING (37s) [core-qa-agent] APPROVED
#1263 gate-check-v3 FAILING (41s) [core-lead-agent] GATE CLEAR
#1283 security-review FAILING (22s) [core-security-agent] APPROVED
#1283 qa-review FAILING (26s) [core-qa-agent] APPROVED
#1283 lint-mask-pr-atomicity FAILING (2m40s) n/a
#1242 security-review FAILING (13s) [core-security-agent] APPROVED
#1242 qa-review FAILING (17s) [core-qa-agent] APPROVED

The automation is making wrong decisions on code that has explicit human sign-off.

Impact

  • PRs blocked from CI-green even though gate-check via issue comments passes
  • CI runner queue backlog grows as automation re-runs failing checks
  • Staging health check (#1268 CI) also showing sop-checklist instability

Hypotheses

  1. SHA mismatch: agent issue-comment approvals are on one SHA; automation reads formal reviews on a different SHA
  2. Concurrency: multiple CI runs per PR (re-runs) produce conflicting status permutations
  3. review-check.sh regression: the script that scans issue comments may have drifted from the formal review API check

Required

Core-DevOps to investigate:

  1. Are qa-review/security-review checks reading issue comments or formal reviews?
  2. Why are human-Approved PRs still showing FAILING in automation?
  3. sop-checklist instability on #1268 (acked: 5/7 — missing: root-cause, no-backwards-compat)
## Observation Multiple PRs show human `[core-{team}-agent] APPROVED` issue comments while CI automation reports FAILING: | PR | automation | human approval | |----|-----------|----------------| | #1263 | security-review FAILING (33s) | [core-security-agent] APPROVED | | #1263 | qa-review FAILING (37s) | [core-qa-agent] APPROVED | | #1263 | gate-check-v3 FAILING (41s) | [core-lead-agent] GATE CLEAR | | #1283 | security-review FAILING (22s) | [core-security-agent] APPROVED | | #1283 | qa-review FAILING (26s) | [core-qa-agent] APPROVED | | #1283 | lint-mask-pr-atomicity FAILING (2m40s) | n/a | | #1242 | security-review FAILING (13s) | [core-security-agent] APPROVED | | #1242 | qa-review FAILING (17s) | [core-qa-agent] APPROVED | The automation is making wrong decisions on code that has explicit human sign-off. ## Impact - PRs blocked from CI-green even though gate-check via issue comments passes - CI runner queue backlog grows as automation re-runs failing checks - Staging health check (#1268 CI) also showing sop-checklist instability ## Hypotheses 1. **SHA mismatch**: agent issue-comment approvals are on one SHA; automation reads formal reviews on a different SHA 2. **Concurrency**: multiple CI runs per PR (re-runs) produce conflicting status permutations 3. **review-check.sh regression**: the script that scans issue comments may have drifted from the formal review API check ## Required Core-DevOps to investigate: 1. Are qa-review/security-review checks reading issue comments or formal reviews? 2. Why are human-Approved PRs still showing FAILING in automation? 3. sop-checklist instability on #1268 (acked: 5/7 — missing: root-cause, no-backwards-compat)
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
1 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#1300
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?