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
[CI] MixedClusterEsqlSpecIT classMethod failing #107879
Comments
Pinging @elastic/es-analytical-engine (Team:Analytics) |
This failed for me (twice) also. Buildscan at https://gradle-enterprise.elastic.co/s/yt6gb6fd5gwm6 |
++, I don't think this is specific to ESQL - maybe some previous tests do not correctly clean stopped/restarted clusters? Both build scans fail after the full cluster restart test, this one also after the rolling upgrade test.
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
@elastic/es-core-infra , I hope it's okay to throw this one your way since it looks similar to past issues, as @astefan has pointed out. |
We're seeing a high number of failures in multi-nodes tests with the nodes failing to start within 2 minutes. This sounds like we may have introduced some change that is slowing down node startup. |
I'm wondering if adding #107619 has triggered this. I think we just cannot have rolling upgrade tests run in parallel like this. I'll open a PR to serialize those tests and see if that stabilizes things a bit. |
Hey, just wanted to say thanks to @mark-vieira and @thecoop for looking into this! |
This fixes #107879 Reduce parallelism for java rest tests for esql
This fixes elastic#107879 Reduce parallelism for java rest tests for esql
Build scan:
https://gradle-enterprise.elastic.co/s/7lya5sv63r7qu/tests/:x-pack:plugin:esql:qa:server:mixed-cluster:v8.14.0%23javaRestTest/org.elasticsearch.xpack.esql.qa.mixed.MixedClusterEsqlSpecIT
Reproduction line:
Applicable branches:
main, 8.14, 8.13
Reproduces locally?:
Didn't try
Failure history:
Failure dashboard for
org.elasticsearch.xpack.esql.qa.mixed.MixedClusterEsqlSpecIT#classMethod
Failure excerpt:
The text was updated successfully, but these errors were encountered: