ci: setup-go cache:false (bind-mount corruption sweep) #2524
Reference in New Issue
Block a user
Delete Branch "fix/setup-go-cache-vs-bind-mount"
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?
Fleet sweep of the mechanism found on cp ci.yml (feat/cp672 branch): actions/setup-go cache:true untars over the runner bind-mounted GOCACHE -> File exists -> Failed to restore -> PARTIAL build cache -> deterministic failures on type-loading/heavy-link jobs (go-arch-lint without-types, test -race too-many-errors), while plain go build silently rebuilds. The runner-level persistent cache (operator-config#184/#190) supersedes actions/cache entirely. URGENT-ish: every PR in this repo rolls the dice until merged.
Holding — this is a core repo under the full SOP gate, and the gate is genuinely red, not satisfiable by reviewer-persona PR approvals. Required contexts failing:
sop-checklist / all-items-acked(0/7 acked, checklist body unfilled — missing comprehensive-testing, local-postgres-e2e, staging-smoke +4),qa-review / approved,security-review / approved, andgate-check-v3 / gate-check. These flip only via the full SOP ceremony (filled+acked checklist → gate eval posts the qa/security statuses); a core-qa/core-security GIT review approval does not flip them.E2E Staging SaaSis also red (the known-flaky staging e2e, cp#245 class). Next step is the author completing the SOP checklist ack on this PR. Not force-merging over a red required gate.qa 1st-lane (5-axis, full diff read) — APPROVE. CI-infra fix, sound.
NOT merge-ready on my lane: this is 0->1 genuine. Needs a 2nd distinct genuine lane (the security-review pull_request_target gate is red pending a security approve). HOLDING for the 2nd lane; will run the authoritative merge-probe once it lands (gate-check-v3=failure + sop-checklist + the E2E-staging reds are the proven non-BP-required class — concluded-non-required is ignored by the merge-check; the probe is the arbiter).
Security 5-axis — APPROVE. Per f35a3134 (approve-then-probe).
CI-only change:
cache:falseadded to SHA-pinnedactions/setup-go(@40f1582b2485089dde7abd97c1529aa768e1baff) across 6 e2e workflows — the core-side fleet-sweep of the GOCACHE/GOMODCACHE bind-mount corruption fix (cp#698/330c12cd class).Non-required reds (E2E Staging SaaS full-lifecycle — outside the green required-aggregate; Local-Provision stub; gate-check-v3; qa/security bot pull_request_target) are not blocking; the merge-probe is the authoritative arbiter (probe-over-flag). No security issues. APPROVE on the current full head; merge via probe (200) by a non-author.