ci: flip platform-build continue-on-error true→false (mc#774 fix-forward landed) #935
No reviewers
Labels
No Label
merge-queue
merge-queue
merge-queue
merge-queue-hold
release-blocker
release-test
security
test-label-sre
tier:high
tier:low
tier:medium
triage-test
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: molecule-ai/molecule-core#935
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "ci/platform-build-flip-coe"
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?
Summary
RFC#219 Phase 4 §2: flip
continue-on-error: true → falseon theplatform-buildjob in.gitea/workflows/ci.yml.Background
Phase 4 (#656) originally flipped platform-build to
continue-on-error: falseon 2026-05-12, but two failure classes then surfaced on commit0e5152c3:Failure class (2) does NOT block this flip: the diagnostic step that exercises it already carries its own step-level
continue-on-error: true(line 203).Verification
CI / Platform (Go) (push)status on main HEAD68560cec: success (8s).Changes
.gitea/workflows/ci.yml: Flipcontinue-on-error: true → falseon platform-build job; update comment to reflect mc#774 closure.🤖 Generated with Claude Code
RFC#219 Phase 4 §2 flip: platform-build continue-on-error: true→false. Verified: CI / Platform (Go) = success on main HEAD. mc#762 tracked separately for mcp_test.go:433.
/sop-ack comprehensive-testing
/sop-ack local-postgres-e2e
/sop-ack staging-smoke
/sop-ack five-axis-review
/sop-ack memory-consulted
orchestrator LGTM — tier:low CI flip only, mc#774