![]() With `replace-evt` the time that the system needs to wake up to check the event can drift later, but scheduling state was carried in a way that works only if the wake-up time drifts earlier. Unfortunately, I don't know how to write a test for this bug. The usual stategy of using `system-idle-evt` to detect busy waiting doesn't work here, because the business happens despite the scheduler's conclusion that the system is idle. As reported by Jan Dvořák on the mailing list. |
||
---|---|---|
.. | ||
collects | ||
src | ||
.gitignore |