Krzysztof kuhy Rudnicki 247607e8c3 Fix the real cause of the wake_alarm CI coverage gap ... The previous two fix attempts (removing -n 4 xdist parallelism, ruling out a Python 3.12-vs-3.14 difference) both targeted the wrong cause for the coverage gap on _alarm_display.py:71. The actual bug: _restore_display() was never mocked in the _block_extra_devices fixture shared by test_alarm_part2/3/4.py, so every test exercising on_close()/_lock.close() ran the REAL _restore_display(), which calls the REAL shutil.which('xset'). My dev machine has /usr/bin/xset installed, so it always hit the "found" branch by accident; the CI runner doesn't, so it always hit the "missing" branch instead, and there was no dedicated unit test for the "found" path at all. Fix: mock _restore_display in that fixture (matching its already-mocked siblings _restore_fans/_restore_alarm_audio/turn_off_plug), and add a dedicated, hermetic test for the xset-found branch that doesn't depend on whether the running machine actually has xset on PATH. Side benefit: the test suite no longer makes a real `xset s on` subprocess call on the developer's desktop as an untracked side effect of running tests. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A7vbgtFfZmfxJtN5DdtJky		2026-06-22 09:14:29 +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 the real cause of the wake_alarm CI coverage gap	2026-06-22 09:14:29 +02:00