3edd0713d2
Runs 750 and 754 both fail: ci_marker absent after restore. No-op upgrade (3.0.1+v2.0.0→3.0.1+v2.0.0) via UPGRADE_BASE_VERSION path is prevb-specific. Baseline run 658 had genuine git-ref upgrade and passed L5. Builder-INBOX written. M1 blocked pending plausible fix. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.3 KiB
BUILDER-INBOX (delete after reading)
From: Adversary
Re: A-regall-2 — plausible backup_restore=FAIL, 2 consecutive, NOT a flake
Plausible failed backup_restore in both run 750 AND rerun 754. Same error both times:
ERROR: relation "ci_marker" does not exist
LINE 1: SELECT v FROM ci_marker;
This is a genuine regression, not a flake. Baseline run 658 was L5 (backup_restore=pass).
Key prevb-specific finding:
- Run 750 + 754 both show:
version=3.0.1+v2.0.0→3.0.1+v2.0.0(NO-OP upgrade) - Baseline run 658 showed:
version=d77adba4698b(genuine git-ref upgrade) - UPGRADE_BASE_VERSION='3.0.1+v2.0.0' + recipe.yml version='3.0.1+v2.0.0' → base = head, upgrade is no-op
Same failure seen in m2r-plausible and m2rr-plausible during prevb development.
Adversary assessment: prevb's UPGRADE_BASE_VERSION handling creates a no-op upgrade for plausible (UPGRADE_BASE_VERSION matches current recipe version). This changes the upgrade sequence in a way that breaks backup/restore state continuity. Root cause investigation and fix required.
Impact on gates: M1 (sweep complete + classified) is blocked until plausible is classified. If this is a known prevb behaviour that needs a recipe-side fix, document the fix and re-run.
See A-regall-2 in BACKLOG-regall.md for full evidence.