admin
9c69b3ff07
gates / gates (push) Successful in 27s
Evidence off the machine at the end of the phases that produced it (R-320). Teardown follows. PHASE 2 — the two database engines, through the REAL Update button: - MariaDB 11.6 -> 12.3 on nextcloud: PROVEN, and pressed through the button for the first time. All four SPIKE-r459 observables: the datadir's own record moved 11.6.2 -> 12.3.3; the engine itself says "already upgraded ... no need to run mariadb-upgrade again"; the entrypoint says "Major version upgrade detected ... Check required!" and then STARTED and FINISHED it (not the `skipped due to $MARIADB_AUTO_UPGRADE` line R-459 feared); and the engine took its own pre-upgrade backup, 631 905 B. The seeded Nextcloud account read back. - PostgreSQL 16 -> 17 on docmost: FAILED exactly as R-463 predicted and nobody had measured. 5.1 s to held; the pin named 17 while nothing ran; the restore brought it back in 29.1 s. The engine's REFUSAL LINE was destroyed by failAndHold before any probe could read it, so it was REPRODUCED INDEPENDENTLY with a control on every step (R-320). PHASE 3 — the bad days. B1 produced THE UNATTENDED HOLD, which this project has never had: the caller pressed once with nobody watching, the app held after 312.9 s, and passes 2 and 3 pressed nothing. B2 put the pin back on a pull failure in 1.0 s. B3 refused `busy` six times. B4 showed there is NO single-flight — 5 of 5 updates ran at once and all ended honest. B5 cut the power in `backing-up` and the box recovered itself and said so. B7 refused under the 2 GB floor. B9 found R-458's risk narrower than the row states. PHASE 4 — every badge on the box is TRUE, and the held app answers all four of Q4's questions. FINDINGS, five new and three corrections to existing rows. The one that matters: R-618 is P1 — two templates name a health probe the app does not answer, and because the guarded update waits on that same probe, a SUCCESSFUL update ends by STOPPING a working app. Measured: tandoor served HTTP 200 on the new version at four samples across five minutes and was then stopped. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
16 lines
1.4 KiB
Plaintext
16 lines
1.4 KiB
Plaintext
22:06:29 ==== B4 [five]: pressing Update on ['privatebin', 'bentopdf', 'wishlist', 'uptime-kuma', 'opengist'] at once
|
|
22:06:29 press wishlist +0.359s http=202 reason=None ::
|
|
22:06:29 press uptime-kuma +0.380s http=202 reason=None ::
|
|
22:06:29 press privatebin +0.399s http=202 reason=None ::
|
|
22:06:30 press opengist +0.446s http=202 reason=None ::
|
|
22:06:30 press bentopdf +0.448s http=202 reason=None ::
|
|
22:06:30 all 5 presses issued within 0.448s
|
|
22:06:30 + 0.1s updating=5 privatebin=safety-dump bentopdf=safety-dump wishlist=pulling uptime-kuma=pulling opengist=pinning
|
|
22:06:41 + 11.7s updating=1 privatebin=done bentopdf=done wishlist=verifying uptime-kuma=done opengist=done
|
|
22:06:47 MOST UPDATES IN FLIGHT AT ONCE: 5 of 5
|
|
22:06:50 privatebin ended phase=done err=None hold=None pinned={'privatebin': 'localhost:5000/drill/paste:2.0.1'}
|
|
22:06:52 bentopdf ended phase=done err=None hold=None pinned={'bentopdf': 'localhost:5000/drill/pdf:2.0.1'}
|
|
22:06:54 wishlist ended phase=done err=None hold=None pinned={'wishlist': 'localhost:5000/drill/wishes:2.0.1'}
|
|
22:06:56 uptime-kuma ended phase=done err=None hold=None pinned={'uptime-kuma': 'localhost:5000/drill/status:2.0.1'}
|
|
22:06:58 opengist ended phase=done err=None hold=None pinned={'opengist': 'localhost:5000/drill/gist:2.0.1'}
|