hub (unreleased): the operator is told when a box's clock is more than one minute from the hub's (R-1384, D79)
gates / gates (push) Successful in 2m11s

The host report's new sent_at (the box clock at the moment of sending) is compared with the hub's clock at arrival.
Both directions; told once; clears within 30 s. A report that waited on the box raises nothing (reported_at is not
read). A second box off in the same direction points at the hub's own clock. Operator-only. Not deployed.

Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
admin committed 2026-11-14 17:05:40 +01:00
1 parent 26f4f7660c
commit 88e636445a
9 files changed
+318 -2

No files matched your search

@@ -0,0 +1,18 @@
== MUTATION: no stamp at sending (the caller's old value leaves)
RED on the mutant, GREEN on the real file
--- FAIL: TestReport_StampsSentAtAtSending (0.01s)
client_sentat_test.go:43: send 0: sent_at is 40m0.011108314s old, want the moment of sending (reported_at was 40 minutes old)
client_sentat_test.go:43: send 1: sent_at is 40m0.011177234s old, want the moment of sending (reported_at was 40 minutes old)
client_sentat_test.go:51: the second send carries 2026-11-14 15:20:41.341281174 +0000 UTC, not after the first 2026-11-14 15:20:41.341281174 +0000 UTC — the stamp is not taken per send
== MUTATION: the stamp is the collect time
RED on the mutant, GREEN on the real file
--- FAIL: TestReport_StampsSentAtAtSending (0.01s)
client_sentat_test.go:43: send 0: sent_at is 40m0.063148269s old, want the moment of sending (reported_at was 40 minutes old)
client_sentat_test.go:43: send 1: sent_at is 40m0.063229086s old, want the moment of sending (reported_at was 40 minutes old)
client_sentat_test.go:51: the second send carries 2026-11-14 15:20:43 +0000 UTC, not after the first 2026-11-14 15:20:43 +0000 UTC — the stamp is not taken per send
== MUTATION: the stamp is taken once and kept
RED on the mutant, GREEN on the real file
--- FAIL: TestReport_StampsSentAtAtSending (0.01s)
client_sentat_test.go:51: the second send carries 2026-11-14 16:00:44.697310482 +0000 UTC, not after the first 2026-11-14 16:00:44.697310482 +0000 UTC — the stamp is not taken per send
3 mutations, 0 not a red-proof
@@ -0,0 +1,44 @@
== MUTATION: the hub reads reported_at (the collect time) instead of the send time — a report that waited alarms
RED on the mutant, GREEN on the real file
--- FAIL: TestBoxClock_AQueuedReportRaisesNothing (0.05s)
box_clock_test.go:104: a report that waited on the box raised 2 wrong, 0 ok — an old reported_at is not a wrong clock
== MUTATION: only a box that is AHEAD is judged (the old tunnel-handshake shape)
RED on the mutant, GREEN on the real file
--- FAIL: TestBoxClock_BothDirectionsOnceThenClear (0.10s)
box_clock_test.go:68: wrong=0 ok=0, want ONE alarm for two reports of the same wrong clock
== MUTATION: the alarm is not remembered — every report alarms again
RED on the mutant, GREEN on the real file
--- FAIL: TestBoxClock_BothDirectionsOnceThenClear (0.11s)
box_clock_test.go:68: wrong=2 ok=0, want ONE alarm for two reports of the same wrong clock
box_clock_test.go:68: wrong=2 ok=0, want ONE alarm for two reports of the same wrong clock
== MUTATION: the alarm never clears
RED on the mutant, GREEN on the real file
--- FAIL: TestBoxClock_BothDirectionsOnceThenClear (0.13s)
box_clock_test.go:85: after the clock came back: wrong=1 ok=0 ([]), want one recovery
box_clock_test.go:85: after the clock came back: wrong=1 ok=0 ([]), want one recovery
== MUTATION: the alarm line is 30 s, not one minute
RED on the mutant, GREEN on the real file
--- FAIL: TestBoxClock_BothDirectionsOnceThenClear (0.09s)
box_clock_test.go:62: a clock under one minute off raised 1 wrong, 0 ok
box_clock_test.go:62: a clock under one minute off raised 1 wrong, 0 ok
== MUTATION: the clear line equals the alarm line (a clock at the edge flaps)
RED on the mutant, GREEN on the real file
--- FAIL: TestBoxClock_BothDirectionsOnceThenClear (0.10s)
box_clock_test.go:79: between the two lines: wrong=1 ok=1, want 1 and 0
box_clock_test.go:79: between the two lines: wrong=1 ok=1, want 1 and 0
== MUTATION: the hub's-own-clock hint ignores the direction
RED on the mutant, GREEN on the real file
--- FAIL: TestBoxClock_SecondBoxSameDirectionPointsAtTheHub (0.05s)
box_clock_test.go:125: boxes off in OPPOSITE directions must not point at the hub: The clock of h2 is 180 seconds behind of the hub's clock. A box with a wrong clock refuses signed jobs and stamps its backups with a wrong time. Re
== MUTATION: no hint at the hub's own clock
RED on the mutant, GREEN on the real file
--- FAIL: TestBoxClock_SecondBoxSameDirectionPointsAtTheHub (0.05s)
box_clock_test.go:137: wrong=3; the second box ahead must name the hub's clock and h1: "The clock of h2 is 179 seconds ahead of the hub's clock. A box with a wrong clock refuses signed jobs and stamps its backups with a wrong time
8 mutations, 0 not a red-proof
== MUTATION: the clock events reach the household (not operator-only)
RED on the mutant, GREEN on the real file
--- FAIL: TestBoxClockEventsAreOperatorOnly (0.00s)
box_clock_operator_only_test.go:9: box_clock_wrong must be operator-only
1 mutations, 0 not a red-proof