Scanner status tests no longer depend on a 100 ms timer (closes #124) #132

Merged
clawbot merged 1 commits from issue-124-scanner-test-timers into next 2026-10-04 09:48:51 +02:00
1 Commits
Author SHA1 Message Date
clawbot a192f3928b Scanner status tests no longer depend on a 100 ms timer (closes #124)
check / check (push) Waiting to run
The two status-send tests now call the send directly on a channel nobody
receives from, so a blocking send hangs the test into its timeout instead
of racing a 100 ms timer that a loaded host can miss.

The gpg test for a child holding gpg's output had the same problem: its
100 ms deadline could fire before the fake gpg wrote the PID of sleep,
and the cleanup then failed. The fake gpg now writes that PID to a named
pipe, and the test cancels only after reading it. It then waits up to
10 s for the call, so a call that waits for sleep fails the test and the
cleanup still kills sleep.

Model: opus-5-5
2026-10-04 07:01:17 +00:00