admin
f41a1a0ad8
gates / gates (push) Failing after 18s
Part 2.1's determination is the first artifact: the scratch resolver was consciously OUT OF SCOPE for R-356, not excluded on state-only grounds - established from R-356's own commit 08eb1a6, whose tests say 'the prepared scratch still resolves ... only the DESTINATION moves'. So 07 section 6.3's rule applies and now has a FOURTH consumer, and the section says so. Live evidence: the collision rerun on demo-hp with the sampler positively controlled first (12 locks=1 across a real check, 4 locks=0 quiet), showing unlock --remove-all 0 times where the drill saw it twice; and the proof reaching verdict pass on demo-felhom - the box that could not run it at all - recorded where last_proof_result had been ABSENT every night. Capability map: the off-site proof row now records that the nightly firing IS proven (it ran unattended at 05:30 on demo-hp) and that a driveless box can now be proved. Register: six rows closed and compressed. OPEN 176 -> 170, CLOSED 152 -> 158.
31 lines
1.5 KiB
Plaintext
31 lines
1.5 KiB
Plaintext
=== the collision, three overlap offsets: full restore FIRST, then the check into it ===
|
|
--- restore, then check +1s ---
|
|
t_restore=08:24:09
|
|
[http=302 wall=0.010349s]
|
|
t_check=08:24:10
|
|
"duration_ms":0 "ok":false "skip_reason":"a backup or restore is already running" "skipped":true "ok":true
|
|
--- restore, then check +2s ---
|
|
t_restore=08:24:22
|
|
[http=302 wall=0.010791s]
|
|
t_check=08:24:24
|
|
"duration_ms":39978 "ok":true "skip_reason":"" "skipped":false "ok":true
|
|
--- restore, then check +3s ---
|
|
t_restore=08:25:19
|
|
[http=302 wall=0.011009s]
|
|
t_check=08:25:22
|
|
"duration_ms":0 "ok":false "skip_reason":"a backup or restore is already running" "skipped":true "ok":true
|
|
|
|
=== THE NON-EFFECT: unlock --remove-all must appear in NO argv ===
|
|
'unlock --remove-all' in the sampler: 0
|
|
any 'unlock' at all: 0
|
|
'cleared a stale exclusive lock' in the log: 0
|
|
|
|
=== and the check SKIPPED rather than colliding ===
|
|
integrity: check PASSED in 1m4s (structure, index, and 100% of the pack data re-read)
|
|
integrity: skipped — a backup or restore is already running; due-ness is NOT advanced, so this retries on the next run
|
|
off-box restore refused for kimai (mode=full): another backup/restore op is already running
|
|
off-box restore kimai completed (full=true, async)
|
|
integrity: check PASSED in 40s (structure, index, and 100% of the pack data re-read)
|
|
integrity: skipped — a backup or restore is already running; due-ness is NOT advanced, so this retries on the next run
|
|
off-box restore kimai completed (full=true, async)
|