-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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 test: TestSaramaConsumerWrapper_start_Messages #1314
Comments
Getting different stack trace now:
|
@albertteoh @joe-elliott @annanay25 is anyone interested in trying to fix this test? It's been failing close to 50% of the time. I almost rage-t.Skipped it today, but it's kind of a critical test for the module. |
I can give this a go if there are no takers. |
Key ObservationsSuccess Runs
Example:
Failed Runs
Questions
|
Root Cause HypothesisThe following describes the failure case:
Summary
|
Reproducing the errorPlace a sleep between the message and error handler go routines to ensure that the test calls
|
Proposed Solution
Alternatives ConsideredStart Error Handler first and sleep betweenThat is:
Why not:
Sleep before
|
Agree that more sleeps won't solve the issue - VMs in Travis are unpredictable and may hang for longer than a reasonable sleep interval. Too long sleeps slow down tests. It's great that you found a way to reproduce. It actually points to another possible solution - use a single goroutine for listening to all 3 channels (msgs, errors, and deadlock detector). Based on your analysis it sounds like it may remove the race condition. |
Thanks, @yurishkuro.I think that's a much more elegant solution! |
https://travis-ci.org/jaegertracing/jaeger/jobs/487803410
The text was updated successfully, but these errors were encountered: