molecule-ai/molecule-core
53
0
Fork 2
Code Issues 187 Pull Requests 45 Actions 6 Packages Projects Releases Wiki Activity

prune-stale-e2e-dns: continue-on-error mask needs accurate tracker #3147

New Issue
Open
opened 2026-06-22 03:56:41 +00:00 by agent-dev-a · 0 comments
agent-dev-a commented 2026-06-22 03:56:41 +00:00
Member
Copy Link
Copy Source

The .gitea/workflows/e2e-staging-saas.yml job prune-stale-e2e-dns runs as best-effort post-E2E cleanup and currently uses continue-on-error: true so that transient Cloudflare API failures do not block the merge gate.

This is an intentional fail-soft mask. Per lint-continue-on-error-tracking (Tier 2e), the mask must carry a fresh, open tracker that accurately describes the job's fail-soft risk. The previous tracker (#3140) closed when that PR merged, and #3108 was identified as unrelated.

This issue tracks the decision to either:

  1. Make the cleanup job fail-hard (continue-on-error: false) if we decide a transient CF blip should block merge, or
  2. Keep the fail-soft behavior and renew the tracker comment every 14 days until a durable fix (e.g., idempotent retry/backoff in the prune script) is implemented.

Scope is limited to workflow governance metadata; no runtime behavior change is required immediately.

The `.gitea/workflows/e2e-staging-saas.yml` job `prune-stale-e2e-dns` runs as best-effort post-E2E cleanup and currently uses `continue-on-error: true` so that transient Cloudflare API failures do not block the merge gate. This is an intentional fail-soft mask. Per `lint-continue-on-error-tracking` (Tier 2e), the mask must carry a fresh, open tracker that accurately describes the job's fail-soft risk. The previous tracker (#3140) closed when that PR merged, and #3108 was identified as unrelated. This issue tracks the decision to either: 1. Make the cleanup job fail-hard (`continue-on-error: false`) if we decide a transient CF blip should block merge, or 2. Keep the fail-soft behavior and renew the tracker comment every 14 days until a durable fix (e.g., idempotent retry/backoff in the prune script) is implemented. Scope is limited to workflow governance metadata; no runtime behavior change is required immediately.
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
 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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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