review(regall): BP-1 baseline verified (A-regall-1: mailu upgrade=pass not skip); BP-2 upgrade-base=main-tip confirmed; batch-1 all L5
All checks were successful
continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
This commit is contained in:
@ -54,12 +54,30 @@ complete. Key facts verified independently:
|
||||
|
||||
## Break-it probes log
|
||||
|
||||
### Probe BP-regall-1: planned — baseline spot-verification
|
||||
Will independently pull run records for baseline runs (e.g. run 554 cryptpad, 556 bluesky-pds)
|
||||
and confirm the baseline levels in STATUS match the actual results.json data.
|
||||
### Probe BP-regall-1: COMPLETE @2026-06-17T02:05Z — baseline table mostly accurate, one discrepancy
|
||||
|
||||
### Probe BP-regall-2: planned — upgrade-base resolution cold check
|
||||
When batch 1-2 results are in, cold-inspect one run's log to confirm:
|
||||
- base resolution uses main-tip ref (kind=ref) per prevb logic
|
||||
- `previous/` overlay NOT applied (no previous/ dir for these recipes)
|
||||
- actual upgrade base is a main-tip commit, not a stale static version
|
||||
Cold-verified all 20 baseline runs referenced in STATUS-regall.md:
|
||||
- All runs 556, 554, 541, 510, 692, 657, 695, 608, 522, 553, 523, 524, 525, 526, 656, 529, 558, 528, 658, 531 confirmed level=5 ✓
|
||||
- bluesky-pds (556): upgrade=skip (EXPECTED_NA) ✓ — matches table
|
||||
- mailu (526): upgrade=PASS in actual results.json — table says "skip (no deployable base)" — **DISCREPANCY** (see A-regall-1)
|
||||
- All other recipes: all rungs match the table ✓
|
||||
|
||||
**FINDING A-regall-1 filed** — mailu baseline upgrade rung is "pass" not "skip (no deployable base)".
|
||||
|
||||
### Probe BP-regall-2: COMPLETE @2026-06-17T02:10Z — upgrade-base resolution confirmed correct
|
||||
|
||||
Cold-read Drone logs for gitea run 727 (batch 1):
|
||||
- `upgrade base: kind=ref ref=e6a1cc79e99e (target-branch (main) tip)` — main-tip used as expected ✓
|
||||
- No `previous/` overlay applied (gitea has no previous/ dir) ✓
|
||||
- deploy message: `base = main-tip/ref e6a1cc79e99e → chaos deploy of the checked-out ref (the PR's true predecessor; not a published pin)` ✓
|
||||
- Upgrade sequence: L5, all tiers pass. `test_upgrade_preserves_marker_repo` PASS, `test_lfs_roundtrip` PASS ✓
|
||||
- This confirms the prevb dynamic-base resolution is working correctly in the regall sweep.
|
||||
|
||||
### Batch 1 cold-verified @2026-06-17T02:10Z — all L5, no regressions
|
||||
|
||||
From Drone build API + cc-ci run results.json:
|
||||
- **matrix-synapse** (run 725, Drone 725, PR#4): level=5, all rungs pass (upgrade=pass) ✓
|
||||
- **drone** (run 726, Drone 726, PR#1): level=5, upgrade=pass, backup_restore=skip (expected) ✓
|
||||
- **gitea** (run 727, Drone 727, PR#1): level=5, all rungs pass (upgrade=pass) ✓
|
||||
|
||||
No regressions vs baseline in batch 1. Dynamic base resolution confirmed working (kind=ref, main-tip).
|
||||
|
||||
Reference in New Issue
Block a user