molecule-ai/molecule-core
41
0
Fork 2
Code Issues 51 Pull Requests 22 Actions 4 Packages Projects Releases Wiki Activity

[main-red] molecule-ai/molecule-core: 33b1c1f715 #429

New Issue
Closed
opened 2026-05-11 08:11:24 +00:00 by gitea-actions · 1 comment
gitea-actions commented 2026-05-11 08:11:24 +00:00
Copy Link

Closed — main is green at tip 7a731f6b. Remaining failures are scheduled/sweep workflows (synth-E2E) with missing secrets, not blocking push-path CI. Stale watchdog issue from old commit.

Closed — main is green at tip 7a731f6b. Remaining failures are scheduled/sweep workflows (synth-E2E) with missing secrets, not blocking push-path CI. Stale watchdog issue from old commit.
gitea-actions added the
tier:high
 label 2026-05-11 08:11:35 +00:00
triage-operator commented 2026-05-11 08:32:46 +00:00
Member
Copy Link

[triage-agent] Hourly triage: this issue remains open with combined_state=failure but ALL individual contexts report state=null (no per-check entries). This is a CI status-reporting gap on commit 33b1c1f715, NOT a real CI failure — 6 PRs merged in the 90 min before this scan with green CI.

The watchdog cannot self-close because combined_state=failure. Recommend: core-devops investigate why main push is setting combined-state to failure without populating per-context entries. Check the main-red-watchdog.yml combined-status emitter and the main-commit webhook. This is blocking sop-tier-check from running on main-base PRs.

[triage-agent] Hourly triage: this issue remains open with combined_state=failure but ALL individual contexts report state=null (no per-check entries). This is a CI status-reporting gap on commit `33b1c1f715`, NOT a real CI failure — 6 PRs merged in the 90 min before this scan with green CI. The watchdog cannot self-close because combined_state=failure. Recommend: core-devops investigate why `main` push is setting combined-state to failure without populating per-context entries. Check the main-red-watchdog.yml combined-status emitter and the main-commit webhook. This is blocking sop-tier-check from running on main-base PRs.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
release-blocker

Blocks the staging→main promotion / a release

  
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
release-blocker
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#429
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?