tor-guardmgr wakes arti up every second!
I think this is rather poor. People have spent a lot of effort abolishing high-frequency periodic wakeups, because they waste energy (battery). And apparently, the work done is sufficiently extensive to make a test unreasonably slow.
(The test tor_hsclient::state::test::expiry is using a "giant leap" clock update because otherwise it has to similate every one of these wakeups.
Perhaps tor_hsservice::timeout_track could help.
Old description
cc @gabi-250
Not a huge issue, but state::test::expiry now takes longer to run than any other test in Arti. Perhaps worth fixing if it's easy to do so?
(Found because I use cargo-nextest, which runs everything in parallel and displays the times.)
Edited by Ian Jackson