-
Notifications
You must be signed in to change notification settings - Fork 25k
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
org.elasticsearch.discovery.zen.UnicastZenPingTests testSimplePings failure #26701
Comments
…connectToChannels
Fixed in #26764 :) |
I wonder if we're having the same issue again, see https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+multijob-unix-compatibility/os=debian/185/consoleText We are supposed to connect to all 4 nodes, but we can't:
|
Can confirm that running this locally at about 1k iterations reproduces the error:
|
Turns out the above only holds true for Reenabled test in |
@original-brownbear it's also failing in master:
Not reproducible locally for me. |
20190124224140-D76BF75E-log-2658-3890858197344673937.txt attaching the logs for the above failure (master build |
* Just like elastic#37268 removing another 1s timeout, those are dangerous since they're easily exceeded by an untimely gc pause * Closes elastic#26701
* Just like elastic#37268 removing another 1s timeout, those are dangerous since they're easily exceeded by an untimely gc pause * Closes elastic#26701
Doesn't reproduce locally but here is what CI said:
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-unix-compatibility/os=ubuntu/1531/consoleFull
The failure in CI has tons of other logging around the failure but that logging looks similar to what I get locally when I run the test.
The text was updated successfully, but these errors were encountered: