669795058b
The `test_cleanup()` test for guiprocess was triggering the early timer warning messages because it was using a VeryCourse timer with a 100ms interval. Changed it to to a normal Course timer (the default) for that test. For the `ipc-timeout` timer we know that is happening in the tests on windows. It's being logged in lost of e2e tests, the elapsed times it's logging are between 0 and 0.020s. I'm not sure if it's the right thing to be changing the log level in production code or marking the messages as expected in test code. |
||
|---|---|---|
| .. | ||
| end2end | ||
| helpers | ||
| manual | ||
| unit | ||
| conftest.py | ||
| test_conftest.py | ||