-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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] HeapAttackIT testManyConcat failing #100678
Comments
Pinging @elastic/es-ql (Team:QL) |
Pinging @elastic/elasticsearch-esql (:Query Languages/ES|QL) |
This is not a blocker. Removing the blocker label. |
We continue to have several failures in `HeapAttackIT1 every day. It's across a wide range of tests and recently looks to be mostly timeouts presumably due to the test taking out the test cluster. The nature of this test seems to make it very susceptible to instability. We should probably mute it entirely unless we think there's a simple fix here given how much noise it's creating. |
Pinging @elastic/es-analytics-geo (Team:Analytics) |
This PR enables ESQL heap attack tests. I have run this suite over 500 iterations with different hardware configurations for the last two days, and all have been successful with the changes in #104159. Additionally, this PR adds an action that can trigger OOM to generate a heap dump if a test takes more than 5 minutes. I've seen cases (previously with our CI) where the test didn't result in OOM but was taking too long. Having the ability to inspect the heap in such cases would be beneficial. Closes #103527 Closes #100678
Build scan:
https://gradle-enterprise.elastic.co/s/z27lugpake4um/tests/:x-pack:plugin:esql:qa:server:single-node:javaRestTest/org.elasticsearch.xpack.esql.qa.single_node.HeapAttackIT/testManyConcat
Reproduction line:
Applicable branches:
main
Reproduces locally?:
No
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.xpack.esql.qa.single_node.HeapAttackIT&tests.test=testManyConcat
Failure excerpt:
The text was updated successfully, but these errors were encountered: