-
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
[CI] GeoJdbcSqlSpecIT sometimes fails in static code #42221
Comments
Pinging @elastic/es-search |
For SAML and Kerberos where we have similar issues with 3rd party libaries that are locale dependent we reset the locale to English if it's an unsupported one. |
Two more failures here: Reproduce
Example relevant log:
|
I am on it. Interesting, somehow it works when I run it on command line with this parameter, but fails when it runs in CI. I have an idea how to fix it though. |
Moves the test suppression from @ClassRule to @before, where it is properly handled in the CI build. Fixes elastic#42221
Moves the test suppression from `ClassRule` to `Before`, where it is properly handled in the CI build. Fixes #42221
Moves the test suppression from `ClassRule` to `Before`, where it is properly handled in the CI build. Fixes #42221
Moves the test suppression from `ClassRule` to `Before`, where it is properly handled in the CI build. Fixes #42221
Moves the test suppression from `ClassRule` to `Before`, where it is properly handled in the CI build. Fixes elastic#42221
There is an intermittent failure that is reported as being in
org.elasticsearch.xpack.sql.qa.single_node.GeoJdbcSqlSpecIT classMethod
.An example is https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+multijob-unix-compatibility/os=oraclelinux-6/201/console
The exception is:
I guess it means assumptions inside static initialisation code are not treated differently to other exceptions, and we need to think of an alternative way to mute the problem.
The assumption was recently added in #42200. An example of a build that suffered the underlying problem that caused the muting attempt is https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+intake/1431/
The text was updated successfully, but these errors were encountered: