kent-mcleod
commented
3 years ago Happy to decrease it again.
It should really be something like 3ms so that it doesn't hold up the rest of the tests. But I think enough people are familiar with it taking a couple seconds that it makes them think the timer is broken if it's observed to be significantly faster or slower than a few seconds. I only noticed that it had been changed to 10seconds because I was trying to figure out why the clock frequency for a platform timer seemed wrong.
This test used to previously only wait for 3 ticks but an earlier refactor increased the timeout to 10 seconds for no apparent reason.
Signed-off-by: Kent McLeod kent@kry10.com