![]() The `alarm-evt` tests are inherently racy, since they depend on the scheduler polling quickly enough. The old time values were close enough that a test failure is particularly likely on Windows, where the clock resolution is around 16ms. To reduce failures, make the time differents much bigger. Closes issue #1232 |
||
---|---|---|
.. | ||
mzlib | ||
tests/racket | ||
info.rkt | ||
LICENSE.txt |