From 3c25172dfb1afccca8ce4d2fd2bac8e29a754b38 Mon Sep 17 00:00:00 2001 From: Oliver Kieselbach Date: Thu, 20 Aug 2026 17:47:15 +0200 Subject: [PATCH] test(agent): real two-writer-era CMTrace fixture from session e9753578 Captured from ImeLogs/AgentExecutor.log of the session that exposed the regression (agent 2.0.1410; device booted on the Pacific OOBE default, agent set W. Europe at 12:13:22Z). One file, two writer eras: 371 lines rendered at local hour 05 by a writer still on PDT (UTC-7) and 195 at hour 14 by one already on CEST (UTC+2) - nine hours apart, interleaved, and no line carries a bias suffix, so nothing in the file itself says which is which. Exactly the case the per-file calibration could not express, and the test that was missing. Analysing the archive also turned up a SECOND, independent defect the revert commit did not know about: the agent log reports "IntuneManagementExtension.log writer offset measured 02:00:00" while that file contains ONLY hour-05 lines (2022 of them, zero at hour 14). A +2 measurement is impossible from its own content, so the calibration anchor leaked across file boundaries - files are walked in sorted order and AgentExecutor.log precedes it. Two-eras-per-file and anchor-leak are separate bugs; both must be fixed. Extension is .cmtrace.txt, not .log: *.log is globally gitignored, and a fixture has no reason to claim that extension. Fixture only, nothing consumes it yet - the era-aware calibrator is next. Co-Authored-By: Claude Opus 5 (1M context) --- .../AgentExecutor-two-writer-eras.cmtrace.txt | 41 +++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 src/Agent/AutopilotMonitor.Agent.V2.Core.Tests/Fixtures/AgentExecutor-two-writer-eras.cmtrace.txt diff --git a/src/Agent/AutopilotMonitor.Agent.V2.Core.Tests/Fixtures/AgentExecutor-two-writer-eras.cmtrace.txt b/src/Agent/AutopilotMonitor.Agent.V2.Core.Tests/Fixtures/AgentExecutor-two-writer-eras.cmtrace.txt new file mode 100644 index 00000000..0b26b2bb --- /dev/null +++ b/src/Agent/AutopilotMonitor.Agent.V2.Core.Tests/Fixtures/AgentExecutor-two-writer-eras.cmtrace.txt @@ -0,0 +1,41 @@ +# Real CMTrace lines from session e9753578-b1d8-4188-9151-7545be7e1761 (agent 2.0.1410). +# ImeLogs/AgentExecutor.log - ONE file, TWO writer eras. +# +# The device booted on the Pacific OOBE default; the agent set W. Europe at 12:13:22Z. +# Lines at local hour 05 were rendered by a writer still on PDT (UTC-7), lines at hour 14 +# by one already on CEST (UTC+2) - 9 hours apart, interleaved in the same log. No line +# carries a bias suffix, so nothing in the file itself says which is which. +# +# This is the case that broke the per-file calibration: the anchor is the newest line, so +# its offset was applied to the older era too. Any era-aware calibrator must resolve BOTH +# halves of this file correctly. +# +# era PDT (local 05:xx): 371 lines in the original, era CEST (local 14:xx): 195 + +### --- transition window, verbatim --- + + + + + + + +### --- additional PDT-era samples --- + + + + + + + + + +### --- additional CEST-era samples --- + + + + + + + +