-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Flaky ES test - TestSpanReader_multiRead_followUp_query #1713
Comments
Does it happen on master/head? I think @jpkrohling fixed it in #1703 |
it happened in #1704, I thought after I merged master with @jpkrohling 's fix |
Actually, I think #1703 is a different issue altogether. This failure is with unexpected call to mocked method, which can be caused by race conditions. It failed again in https://travis-ci.org/jaegertracing/jaeger/jobs/568600800#L2885 |
Another recent failure https://travis-ci.org/jaegertracing/jaeger/jobs/582922510 @guanw had a potential explanation in #1786 (comment) |
This test does appear to be time-sensitive: https://travis-ci.org/jaegertracing/jaeger/jobs/593308117 |
@pavolloffay #1703 didn't fix it. The fix was to be less sensitive to the order, but it seems like the issue is with 1 or 2 spans being created, due to the time of day when the test runs and ES queries 1 or 2 daily indices
|
One way to fix it is to pass a "clock" to ES which would always return the same time of day in the test, instead of using time.now() |
I will have a look at this one again |
defined in plugin/storage/es/spanstore/reader_test.go:208
The text was updated successfully, but these errors were encountered: