-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] RestSqlIT testAsyncTextPaginated failing #80089
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
Comments
Pinging @elastic/es-ql (Team:QL) |
There are 4 test classes with the name RestSqlIT
All have had failures in the last 7 days apart from https://build-stats.elastic.co/app/kibana#/discover?_g=h@33d9122&_a=h@19cd33a The test is muted in the base class in #80126 |
The failures won't reproduce locally, but all CI failures contain the warning |
The leftover task is What might be happening is:
If you agree then the fix could be to wait for pending tasks to complete at the end of the previous test. If you search for Please also upvote #65846. |
Maybe this scenario could happen, there are failures occurring when fetching the async results; but there are also failures triggered even by fetching the async task's status (like here and here), or even for starting the async job (like here). Then all failures of this test are 404s vs 503s (as in #65846) and the reason, when available is And it also seems these types of failures for this test started past the 27th last month (there are a couple of other failures, but time out-related). So it might still be the suggested root cause, but I'd like to poke around a bit more. |
Pinging @elastic/es-analytical-engine (Team:Analytics) |
I tested both the failures reported in #76785 as well as reported here for both main (8.15) and 7.17 and all passed locally. However, in one of the above comments it was pointed out that these failures only occur in CI, not locally, and they appear to be unclosed previous async queries. So I'm making a PR that unmutes the test as well as adds the suggested |
To see both 8.15 and 7.17 running in CI, I made two PRs: |
This issue has been closed because it has been open for too long with no activity. Any muted tests that were associated with this issue have been unmuted. If the tests begin failing again, a new issue will be opened, and they may be muted again. |
This issue is getting re-opened because there are still AwaitsFix mutes for the given test. It will likely be closed again in the future. |
Although the same test, this failure differs from #76785, because that was a timeout whereas this one is "all shards failed". I wonder if this is yet another manifestation of #65846?
Build scan:
https://gradle-enterprise.elastic.co/s/xehunhrnkfhhi/tests/:x-pack:plugin:sql:qa:server:security:with-ssl:integTest/org.elasticsearch.xpack.sql.qa.security.RestSqlIT/testAsyncTextPaginated
Reproduction line:
./gradlew ':x-pack:plugin:sql:qa:server:security:with-ssl:integTest' --tests "org.elasticsearch.xpack.sql.qa.security.RestSqlIT.testAsyncTextPaginated" -Dtests.seed=B1D5C515E1E4486D -Dtests.locale=hr-HR -Dtests.timezone=Asia/Irkutsk -Druntime.java=17
Applicable branches:
master, 8.0, 7.16
Reproduces locally?:
No
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.xpack.sql.qa.security.RestSqlIT&tests.test=testAsyncTextPaginated
Failure excerpt:
The text was updated successfully, but these errors were encountered: