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] Failures in various sql tests due to ZoneRulesException: Unknown time-zone ID: Asia/Qostanay #72963
Comments
Pinging @elastic/es-ql (Team:QL) |
Managed to reproduce this one. It's all about the java version.
According to #72490 the Joda version has been updated two days ago to 2.10.10 and the Java 11 version used in CI doesn't seem to be the latest one. With 11.0.11 the issue doesn't reproduce for me.
If I'm not mistaken this update ^ went into 11.0.4 which is consistent with the behavior I see in this test: 11.0.2 complains that |
Relates to #72963. |
Also, the local test that fails on my machine show these logs:
The jvm being used is 11.0.2. The runtime jvm to be used in this test according to the reproduceable command |
Looks like we indeed were not correctly using I've opened #73003 to fix that, but I'm not sure it'll necessarily fix the errors. Athough it at least with make the behavior consistent. |
Not surprisingly my PR picked up a different error. Since we've effectively not been testing against runtime javas properly for who knows how long, my fear is merging the "fix" will break countless other things. That said, if we do have incompatibilities we should probably find out. |
@mark-vieira I've looked at that failure you mentioned. Its root cause is not ES SQL or even Elasticsearch specific imo, but JVM specific. The query that is failing is
Which is surprising given that this has never been caught before. If we test ES on 1.8, both runtime and compilation, this failure should have been caught somehow. To me it looks like different Java behavior unless I'm missing something. |
That's exactly the case. We've only been running integration test clusters using the Gradle JDK (11). So no, we wouldn't have caught it until the fix in that PR. |
Then how about upgrading jdk 11 (and all other JDKs) to the latest, which should have been the like this in the first place? |
I'll reach out to infra to see why these aren't being regularly updated. For some reason it's still 11.0.2. |
I've opened an infra issue to investigate why oracle and openjdk releases seem to be lagging behind on jvm-catalog.elastic.co |
This one is sort of another flavor of the same issue: https://gradle-enterprise.elastic.co/s/mwxjqeyzes2fy |
And another one, not in sql tests: https://gradle-enterprise.elastic.co/s/vl3sa55rd7iey
|
Java 11.0.2 is still on some CI machines - https://gradle-enterprise.elastic.co/s/hqzblhjznqpqg failed due to |
Several SQL test related issues that look the same today, here are a few of them, all on 6.8 an in periodic matrix tests: |
Don't know if this is relevant but some of these have different problematic time zone:
|
Yeah, looks like this is still blowing up on 6.8. |
JDK 11 has been updated on the CI machines and 6.8 has been "fixed" so that test executors and clusters run using the same configured JDK. Is there something else that needs addressing here in unit tests? |
Ok, it seems there are still some of these failures due to our CentOS 6 images not having been updated yet. I've opened https://github.com/elastic/infra/issues/29279 to address this. |
Closing this one now, as there were no more failures in the last week. |
Surprise! Two more failures. Both failed with: Throwable #1: java.time.zone.ZoneRulesException: Unknown time-zone ID: America/Nuuk https://gradle-enterprise.elastic.co/s/6jqxfpy5cjtqe reproduce with:
Runtime info
https://gradle-enterprise.elastic.co/s/zwjln6kii34n2 reproduce with:
Runtime info
|
@benwtrent these failures are not in ES SQL tests. I'd suggest creating a new issue for these specifically. |
Opening new issue: #73899 Even though its probably the same root cause, new issue for tracking work. |
Build scan: multiple. One of them https://gradle-enterprise.elastic.co/s/b5joeiwm33tdm
Repro line:
Reproduces locally?: no
Applicable branches: 6.8
Failure history: started failing on May 11th.
Failure excerpt:
The text was updated successfully, but these errors were encountered: