Skip to content
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

UnicastBackwardsCompatibilityIT fails frequently on 2.1 Windows #15182

Closed
cbuescher opened this issue Dec 2, 2015 · 2 comments
Closed

UnicastBackwardsCompatibilityIT fails frequently on 2.1 Windows #15182

cbuescher opened this issue Dec 2, 2015 · 2 comments
Labels
>test Issues or PRs that are addressing/adding tests >test-failure Triaged test failures from CI

Comments

@cbuescher
Copy link
Member

This test fails quiet frequently over the last few days on 2.1 branch, going through the failure mails it seems its only on Windows 2012 machine. Last seen was

http://build-us-00.elastic.co/job/es_core_21_window-2012/129/

and the top of the stacktrace reads like

java.lang.IllegalStateException: Failed to start elasticserch. Responses: [couldn't find elasticsearch bound to localhost:29301!]
    at __randomizedtesting.SeedInfo.seed([24181440F4C4423C]:0)
    at org.elasticsearch.test.ExternalNodeServiceClient.interact(ExternalNodeServiceClient.java:85)
    at org.elasticsearch.test.ExternalNodeServiceClient.stop(ExternalNodeServiceClient.java:60)
    at org.elasticsearch.test.ExternalNode.stop(ExternalNode.java:231)
    at org.elasticsearch.test.ExternalNode.close(ExternalNode.java:257)
    at org.apache.lucene.util.IOUtils.close(IOUtils.java:97)
    at org.apache.lucene.util.IOUtils.close(IOUtils.java:84)
    at org.elasticsearch.test.CompositeTestCluster.close(CompositeTestCluster.java:266)
    at org.apache.lucene.util.IOUtils.close(IOUtils.java:97)
    at org.elasticsearch.test.ESIntegTestCase.clearClusters(ESIntegTestCase.java:588)
    at org.elasticsearch.test.ESIntegTestCase.afterClass(ESIntegTestCase.java:1978)

Going throught the output it is not clear to me if this is a follow up error cause by something else.

@cbuescher cbuescher added >test Issues or PRs that are addressing/adding tests >test-failure Triaged test failures from CI labels Dec 2, 2015
@nik9000
Copy link
Member

nik9000 commented Dec 2, 2015

If I had to guess blindly I'd guess that I left a bug in ExternalNode that let it try to shut down the node twice. Why it only comes up on windows is a mystery to me though.

@clintongormley
Copy link

Old test failure. Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>test Issues or PRs that are addressing/adding tests >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

3 participants