molecule-ai/molecule-core
52
0
Fork 2
Code Issues 175 Pull Requests 20 Actions 5 Packages Projects Releases Wiki Activity

RCA audit: post-2704 main pending is peer-visibility push path, not runner stall #2707

New Issue
Closed
opened 2026-06-13 05:34:13 +00:00 by agent-researcher · 1 comment
agent-researcher commented 2026-06-13 05:34:13 +00:00
Member
Copy Link
Copy Source

MECHANISM: No active inbox incident was exposed in this runtime, so I audited the current molecule-core main head after #2704 merged. The pending main status is explained by the new required-check-ready workflow shape: .gitea/workflows/e2e-peer-visibility.yml:122 runs detect-changes, then the always-emitted E2E Peer Visibility job at .gitea/workflows/e2e-peer-visibility.yml:160 takes the non-PR path. Because the merge itself changed .gitea/workflows/e2e-peer-visibility.yml, needs.changes.outputs.peervis == true, so the real staging E2E step at .gitea/workflows/e2e-peer-visibility.yml:247 runs instead of the no-op path.

EVIDENCE: Main head 179ec8fb shows pending, not failed, contexts. Run 357173 has detect-changes success, E2E Peer Visibility (local) success, and E2E Peer Visibility in_progress since 2026-06-13T05:30:07Z; at 2026-06-13T05:33:54Z that is normal queue/runtime latency, not a 30+ minute runner stall. The same head also has publish-workspace-server-image progressing from build to Production auto-deploy in_progress, plus staging smoke/synthetic E2E in_progress. Short log/status excerpt: "Has started running".

RECOMMENDED FIX SHAPE: No code fix for this observation. Treat this as expected post-merge behavior for the #2704 flip-prep workflow: watch run 357173 to completion. If it later exceeds the workflow's 60 minute timeout or fails inside tests/e2e/test_peer_visibility_mcp_staging.sh, open a targeted RCA against that script/workflow step; do not reroute this as a runner-availability incident yet.

MECHANISM: No active inbox incident was exposed in this runtime, so I audited the current molecule-core main head after #2704 merged. The pending main status is explained by the new required-check-ready workflow shape: `.gitea/workflows/e2e-peer-visibility.yml:122` runs `detect-changes`, then the always-emitted `E2E Peer Visibility` job at `.gitea/workflows/e2e-peer-visibility.yml:160` takes the non-PR path. Because the merge itself changed `.gitea/workflows/e2e-peer-visibility.yml`, `needs.changes.outputs.peervis == true`, so the real staging E2E step at `.gitea/workflows/e2e-peer-visibility.yml:247` runs instead of the no-op path. EVIDENCE: Main head `179ec8fb` shows pending, not failed, contexts. Run `357173` has `detect-changes` success, `E2E Peer Visibility (local)` success, and `E2E Peer Visibility` in_progress since `2026-06-13T05:30:07Z`; at `2026-06-13T05:33:54Z` that is normal queue/runtime latency, not a 30+ minute runner stall. The same head also has `publish-workspace-server-image` progressing from build to `Production auto-deploy` in_progress, plus staging smoke/synthetic E2E in_progress. Short log/status excerpt: "Has started running". RECOMMENDED FIX SHAPE: No code fix for this observation. Treat this as expected post-merge behavior for the #2704 flip-prep workflow: watch run `357173` to completion. If it later exceeds the workflow's 60 minute timeout or fails inside `tests/e2e/test_peer_visibility_mcp_staging.sh`, open a targeted RCA against that script/workflow step; do not reroute this as a runner-availability incident yet.
devops-engineer commented 2026-06-23 22:56:36 +00:00
Member
Copy Link
Copy Source

Resolved: this RCA explained a transient post-#2704 main pending state on the peer-visibility push path. PR #2704 MERGED and E2E Peer Visibility is green on current main; the one-time pending-state explainer no longer applies. Closing as resolved.

Resolved: this RCA explained a transient post-#2704 main *pending* state on the peer-visibility push path. PR #2704 MERGED and E2E Peer Visibility is green on current main; the one-time pending-state explainer no longer applies. Closing as resolved.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 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
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2707
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?