CI-17: test_peakguard's real-cycle fixture runs at its own instant (host-load independent) #252

Merged

admin merged 2 commits from CI-17 into release/1.0 2026-11-15 00:50:50 +01:00

Conversation 2 Commits 2 Files Changed 1

+38 -16

2 Commits

Author	SHA1	Message	Date
glenn schrooyenandClaude	63043ea219	CI-17 round 2: stale/dead fixtures take rejected_since from the pinned instant; comment made true ... The two fixtures ran their cycles at _SRC_NOW but set rejected_since from the real clock, so the cycle saw inverter-b live while live_units() saw it stale. Both now use _SRC_NOW, and a check asserts both clocks agree. run_cycle's comment no longer claims ctl_cycle.py:49 is the only clock read. Co-Authored-By: Claude <noreply@anthropic.com>	2026-11-14 23:39:49 +01:00
glenn schrooyenandClaude	39ca1df232	CI-17: test_peakguard's real-cycle fixture reads the clock once, so host load cannot add peak@site ... c_src's telegrams were laid up to one datetime.now(); each cycle() then read the real clock again (ctl_cycle.py:49). Under --cpus 0.25 a cycle takes ~1.3 s, so by the 23rd sweep cycle the last telegram was older than max_hold_s (30 s), the guard counted the gap and filed peak@site. The cycles now run AT the fixture's own instant. Test only; the exact-set checks are unchanged. Co-Authored-By: Claude <noreply@anthropic.com>	2026-11-14 22:11:09 +01:00