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

[RFC internal#219 Phase 4 PR-2] Flip continue-on-error true→false on stable CI jobs #623

New Issue
Open
opened 2026-05-12 00:51:49 +00:00 by hongming · 1 comment
hongming commented 2026-05-12 00:51:49 +00:00
Owner
Copy Link
Copy Source

Follow-up to #622. RFC internal#219 Phase 4 step 2 — flip continue-on-error: true → false on the .gitea/workflows/ci.yml jobs that pass reliably on main. Approach: pull last 50 main-branch CI runs, compute per-job pass-rate, flip the ones >=98% green. Do NOT flip flaky jobs — file root-cause investigation issues for those instead (no fix-by-mute). Blocks: requires #622 to land first so all-required catches the flips. Memory ref: feedback_no_such_thing_as_flakes (every intermittent failure is a real bug). Test plan: after flip, open one PR that intentionally fails the flipped job, verify protection blocks merge; revert if any unexpected regressions on main.

Follow-up to #622. RFC internal#219 Phase 4 step 2 — flip continue-on-error: true → false on the .gitea/workflows/ci.yml jobs that pass reliably on main. Approach: pull last 50 main-branch CI runs, compute per-job pass-rate, flip the ones >=98% green. Do NOT flip flaky jobs — file root-cause investigation issues for those instead (no fix-by-mute). Blocks: requires #622 to land first so all-required catches the flips. Memory ref: feedback_no_such_thing_as_flakes (every intermittent failure is a real bug). Test plan: after flip, open one PR that intentionally fails the flipped job, verify protection blocks merge; revert if any unexpected regressions on main.
hongming added the tier:high label 2026-05-12 00:51:49 +00:00
core-devops was assigned by hongming 2026-05-12 00:51:49 +00:00
hongming-codex-laptop commented 2026-05-12 19:54:55 +00:00
Member
Copy Link
Copy Source

Hourly CI/CD triage evidence (hongming-codex-laptop, 2026-05-12T19:50Z): lint-continue-on-error-tracking is now a current merge blocker on multiple PR heads.

Verified PR #755 run 18587: the lint emits untracked continue-on-error: true errors across workflows including e2e-staging-saas.yml, e2e-staging-sanity.yml, gate-check-v3.yml, handlers-postgres-integration.yml, harness-replays.yml, lint-workflow-yaml.yml, publish-canvas-image.yml, redeploy-tenants-on-main.yml, redeploy-tenants-on-staging.yml, staging-verify.yml, and others. The required fix class is tracker comments or removing the masks, not rerunning CI.

Hourly CI/CD triage evidence (hongming-codex-laptop, 2026-05-12T19:50Z): `lint-continue-on-error-tracking` is now a current merge blocker on multiple PR heads. Verified PR #755 run 18587: the lint emits untracked `continue-on-error: true` errors across workflows including `e2e-staging-saas.yml`, `e2e-staging-sanity.yml`, `gate-check-v3.yml`, `handlers-postgres-integration.yml`, `harness-replays.yml`, `lint-workflow-yaml.yml`, `publish-canvas-image.yml`, `redeploy-tenants-on-main.yml`, `redeploy-tenants-on-staging.yml`, `staging-verify.yml`, and others. The required fix class is tracker comments or removing the masks, not rerunning CI.
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 core-devops
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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