[CI] LangPainlessClientYamlTestSuiteIT test {yaml=painless/20_scriptfield/Scripted Field with error accessing an unsupported field via the script fields api} failing #79986
Assignees
Labels
:Core/Infra/Scripting
Scripting abstractions, Painless, and Mustache
Team:Core/Infra
Meta label for core/infra team
>test-failure
Triaged test failures from CI
Comments
ywangd
added
:Core/Infra/Scripting
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
|
It looks like one shard is empty and so not all shards have failures, leading to a success response. |
stu-elastic
added a commit
to stu-elastic/elasticsearch
that referenced
this issue
Oct 28, 2021
The 20_scriptfield:"Scripted Field with error accessing an unsupported field via the script fields api" test expects to fail because the field is not yet supported in the fields API. However, if the number of shards in the target index is randomly more than one, the empty shard will succeed leading to a 200 response rather than the expected 400 response. This change forces the number of shards to 1 to avoid this scenario. Fixes: elastic#79986
stu-elastic
added a commit
that referenced
this issue
Oct 28, 2021
The 20_scriptfield:"Scripted Field with error accessing an unsupported field via the script fields api" test expects to fail because the field is not yet supported in the fields API. However, if the number of shards in the target index is randomly more than one, the empty shard will succeed leading to a 200 response rather than the expected 400 response. This change forces the number of shards to 1 to avoid this scenario. Fixes: #79986
stu-elastic
added a commit
to stu-elastic/elasticsearch
that referenced
this issue
Oct 28, 2021
The 20_scriptfield:"Scripted Field with error accessing an unsupported field via the script fields api" test expects to fail because the field is not yet supported in the fields API. However, if the number of shards in the target index is randomly more than one, the empty shard will succeed leading to a 200 response rather than the expected 400 response. This change forces the number of shards to 1 to avoid this scenario. Fixes: elastic#79986 Backport: 9511c54
stu-elastic
added a commit
that referenced
this issue
Oct 28, 2021
The 20_scriptfield:"Scripted Field with error accessing an unsupported field via the script fields api" test expects to fail because the field is not yet supported in the fields API. However, if the number of shards in the target index is randomly more than one, the empty shard will succeed leading to a 200 response rather than the expected 400 response. This change forces the number of shards to 1 to avoid this scenario. Fixes: #79986 Backport: 9511c54
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This failed on my PR and is reproducible
Build scan:
https://gradle-enterprise.elastic.co/s/co5sy2mcxu2xg/tests/:modules:lang-painless:yamlRestTest/org.elasticsearch.painless.LangPainlessClientYamlTestSuiteIT/test%20%7Byaml=painless%2F20_scriptfield%2FScripted%20Field%20with%20error%20accessing%20an%20unsupported%20field%20via%20the%20script%20fields%20api%7D
Reproduction line:
./gradlew ':modules:lang-painless:yamlRestTest' --tests "org.elasticsearch.painless.LangPainlessClientYamlTestSuiteIT.test {yaml=painless/20_scriptfield/Scripted Field with error accessing an unsupported field via the script fields api}" -Dtests.seed=18C365613D7AD5B6 -Dtests.locale=de-DE -Dtests.timezone=SystemV/CST6 -Druntime.java=17Applicable branches:
master, 8.0
Reproduces locally?:
Yes
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.painless.LangPainlessClientYamlTestSuiteIT&tests.test=test%20%7Byaml%3Dpainless/20_scriptfield/Scripted%20Field%20with%20error%20accessing%20an%20unsupported%20field%20via%20the%20script%20fields%20api%7D
Failure excerpt:
The text was updated successfully, but these errors were encountered: