[CI] RuntimeFieldsClientYamlTestSuiteIT test {yaml=runtime_fields/100_geo_point/geo shape query} failing #107504
Assignees
Labels
:Analytics/Geo
Indexing, search aggregations of geo points and shapes
low-risk
An open issue or test failure that is a low risk to future releases
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
>test-failure
Triaged test failures from CI
Comments
kkrik-es
added
:Analytics/Geo
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
iverase
added
low-risk
|
It seems it is a issue with jni and java 17. Changing the java runtime to 21 fix it. This always fails: |
|
Another failure, again with jdk17: https://gradle-enterprise.elastic.co/s/xmovg3depceui |
|
Another one: https://gradle-enterprise.elastic.co/s/k2vxkzyfy2cra |
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this issue
May 2, 2024
JNA supports two types of mapping to native methods, proxying and direct method mapping. Proxying is nicer for unit testing, but unfortunately the proxied methods are lazily loaded. NativeAccess expects that methods are linked during static init, before SecurityManager is initialized. For any native methods called after security manager init, the proxied method will fail. This commit changes the zstd bindings to use direct method mapping so that calling zstd methods does not fail when using JNA (pre Java 21). closes elastic#107504 closes elastic#107770
rjernst
added a commit
that referenced
this issue
May 2, 2024
JNA supports two types of mapping to native methods, proxying and direct method mapping. Proxying is nicer for unit testing, but unfortunately the proxied methods are lazily loaded. NativeAccess expects that methods are linked during static init, before SecurityManager is initialized. For any native methods called after security manager init, the proxied method will fail. This commit changes the zstd bindings to use direct method mapping so that calling zstd methods does not fail when using JNA (pre Java 21). closes #107504 closes #107770
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this issue
May 2, 2024
JNA supports two types of mapping to native methods, proxying and direct method mapping. Proxying is nicer for unit testing, but unfortunately the proxied methods are lazily loaded. NativeAccess expects that methods are linked during static init, before SecurityManager is initialized. For any native methods called after security manager init, the proxied method will fail. This commit changes the zstd bindings to use direct method mapping so that calling zstd methods does not fail when using JNA (pre Java 21). closes elastic#107504 closes elastic#107770
elasticsearchmachine
pushed a commit
that referenced
this issue
May 2, 2024
JNA supports two types of mapping to native methods, proxying and direct method mapping. Proxying is nicer for unit testing, but unfortunately the proxied methods are lazily loaded. NativeAccess expects that methods are linked during static init, before SecurityManager is initialized. For any native methods called after security manager init, the proxied method will fail. This commit changes the zstd bindings to use direct method mapping so that calling zstd methods does not fail when using JNA (pre Java 21). closes #107504 closes #107770
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There were two failures in the past few days,
https://gradle-enterprise.elastic.co/s/emrozphiy7tpo
Build scan:
https://gradle-enterprise.elastic.co/s/h6snbby5vj7qo/tests/:modules:runtime-fields-common:yamlRestTest/org.elasticsearch.painless.RuntimeFieldsClientYamlTestSuiteIT/test%20%7Byaml=runtime_fields%2F100_geo_point%2Fgeo%20shape%20query%7D
Reproduction line:
Applicable branches:
main
Reproduces locally?:
Didn't try
Failure history:
Failure dashboard for
org.elasticsearch.painless.RuntimeFieldsClientYamlTestSuiteIT#test {yaml=runtime_fields/100_geo_point/geo shape query}Failure excerpt:
The text was updated successfully, but these errors were encountered: