molecule-ai/molecule-core
44
0
Fork 2
Code Issues 134 Pull Requests 156 Actions Packages Projects Releases Wiki Activity

[main-red] molecule-ai/molecule-core: e70955298b #481

New Issue
Closed
opened 2026-05-11 13:06:36 +00:00 by gitea-actions · 0 comments
gitea-actions bot commented 2026-05-11 13:06:36 +00:00
Copy Link
Copy Source

SRE investigation: NOT a real failure — Gitea combined-status bug

All 22 status contexts have state: null (no runner has reported yet). Per runbooks/gitea-operational-quirks.md §Gitea-combined-status-false-positive: Gitea reports combined state as failure when ALL individual contexts have state: null.

This is the Gitea Actions combined-status false-positive, NOT a real CI failure.

Evidence: Every context in the failure report has "state": null — meaning no Gitea runner has reported a status for that context yet. The combined_state: "failure" is Gitea's bug (it conflates "no status yet" with "failed").

No action needed. The individual runners are still running their scheduled jobs. When they complete, their individual state fields will be populated and the combined state will reflect reality.

Cross-reference: This is the same class of Gitea bug documented in runbooks/gitea-operational-quirks.md (SRE PR #478 pending). The workaround is: always check individual context state fields, never the combined state.

Closing as non-actionable flake (Gitea bug).

## SRE investigation: NOT a real failure — Gitea combined-status bug All 22 status contexts have `state: null` (no runner has reported yet). Per `runbooks/gitea-operational-quirks.md` §Gitea-combined-status-false-positive: **Gitea reports combined state as `failure` when ALL individual contexts have `state: null`.** This is the Gitea Actions combined-status false-positive, NOT a real CI failure. **Evidence:** Every context in the failure report has `"state": null` — meaning no Gitea runner has reported a status for that context yet. The `combined_state: "failure"` is Gitea's bug (it conflates "no status yet" with "failed"). **No action needed.** The individual runners are still running their scheduled jobs. When they complete, their individual `state` fields will be populated and the combined state will reflect reality. **Cross-reference:** This is the same class of Gitea bug documented in `runbooks/gitea-operational-quirks.md` (SRE PR #478 pending). The workaround is: always check individual context `state` fields, never the combined state. Closing as non-actionable flake (Gitea bug).
gitea-actions bot added the tier:high label 2026-05-11 13:06:38 +00:00
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 tier:high
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm 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) hongming hongming-codex-laptop hongming-kimi-laptop hongming-pc2 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 plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot 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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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