Krzysztof kuhy Rudnicki 20d5d1f89b fix(usage_report): stop charging atop's HZ field as CPU; bundle since-last-report mode ... atop's `-P PRC` output inserts the clock-tick rate (HZ=100) between the `state` and `utime` columns. Both the Python parser and the native C aggregator read that constant as utime for every record, charging a flat 1 CPU-second per record — so cpu_seconds collapsed to pid_count and short-lived fork-storm commands (xset, dd, chronyc) topped the CPU table (xset showed 67h). The old test fixtures lacked the HZ field, so code and tests agreed on the bug. - _parse_prc / atop_agg.c: read utime/stime past the HZ field (after+2/+3, tokens[10]/[11]); bump the length guards accordingly - restore C/atop_agg (deleted in 89b4f59) under linux_configuration/C/, where the build path resolves; corrected test fixtures to include HZ - _atop_agg_binary: fall back to the Python parser when the C source tree is gone instead of trusting an orphaned cached binary - add regression tests proving HZ is not summed as CPU - bundle the in-progress since-last-report multi-day aggregation (segments, -b/-e bounding, persisted state, window merging) and its tests/conftest - meta: gate linux_configuration/tests in pytest_changed_packages.py Verified by running usage_report.py --date 20260604: Top CPU now led by SkyrimSE; xset/dd/chronyc fall to ~0. C unit tests + full pytest suite green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-04 18:13:47 +02:00
..
cleanup-2026-05	chore: spring-clean repo root (move docs, relocate batch3 script, drop stale outputs)	2026-05-14 20:01:09 +02:00
superpowers	fix(usage_report): stop charging atop's HZ field as CPU; bundle since-last-report mode	2026-06-04 18:13:47 +02:00