recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

review(regall): A-regall-2 CONFIRMED — plausible backup_restore=fail 2/2 (genuine regression)
All checks were successful
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone Build is passing
Details

Browse Source 
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>
This commit is contained in:
autonomic-bot
2026-06-17 02:34:04 +00:00
parent a7317a54fb
commit 3edd0713d2
3 changed files with 47 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
machine-docs/BACKLOG-regall.md
View File

@ -58,13 +58,24 @@
- Hypothesis: prevb's new base-resolution path resolves UPGRADE_BASE_VERSION to a static version; if recipe.yml also pins that same version, the upgrade is a no-op, which may change the DB state sequence enough to break backup/restore
- Same failure pattern in m2r-plausible and m2rr-plausible (prevb development runs) — both level=2, backup_restore=fail
**Builder rerun:** Drone 754 (triggered after 750 failed) — verdict pending.
**Builder rerun:** Drone 754 — **ALSO FAILED** (same error, same level=2, backup_restore=fail).
**Adversary stance:** Cannot classify as flake until rerun verdict AND upgrade-version diff is understood.
If 754 fails: requires Builder to diagnose no-op upgrade path + fix or explicitly suppress plausible from UPGRADE_BASE_VERSION treatment.
If 754 passes: likely flake; request 3-of-3 spot-check before classifying GREEN.
**Adversary verdict: GENUINE REGRESSION (2/2 runs failed) — NOT a flake.**
**Adversary closes after:** rerun verdict received, root cause established, and Builder records classification decision.
Both runs 750 and 754:
- `version=3.0.1+v2.0.0→3.0.1+v2.0.0` (no-op upgrade via UPGRADE_BASE_VERSION)
- `ERROR: relation "ci_marker" does not exist` after restore
- Backup test passes (artifact only, not content)
- Restore test fails
**Required:** Builder must diagnose the no-op upgrade path and either:
(a) Fix the backup/restore to work correctly under same-version upgrades, OR
(b) Update UPGRADE_BASE_VERSION to an older version so upgrade is genuine, OR
(c) Document why plausible backup_restore is not feasible and mark as known-fail
Builder-INBOX written @2026-06-17T03:30Z with full details.
**Adversary closes after:** Builder fixes + re-run shows backup_restore=pass.
---