-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
contact::tests::test_was_seen_recently is flaky #5440
Comments
This is before #5436 is merged |
#5436 is only about |
I can reliably reproduce this on my computer with |
For now only in `test_was_seen_recently()`, looks like it's the only one failing because of system time jumps caused by `SystemTime::shift()` called from other tests in parallel. Add `SystemTimeTools::lock()` for this so that tests calling `SystemTime::shift()` wait for critical sections in parallel running tests to be done.
For now only in `test_was_seen_recently()`, looks like it's the only one failing because of system time jumps caused by `SystemTime::shift()` called from other tests in parallel. Add `SystemTimeTools::lock()` for this so that tests calling `SystemTime::shift()` wait for critical sections in parallel running tests to be done.
For now only in `test_was_seen_recently()`, looks like it's the only one failing because of system time jumps caused by `SystemTime::shift()` called from other tests in parallel. Add `SystemTimeTools::lock()` for this so that tests calling `SystemTime::shift()` wait for critical sections in parallel running tests to be done.
In CI this is fixed (worked around) by #5457 |
Log of failure from CI:
The text was updated successfully, but these errors were encountered: