-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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] org.elasticsearch.backwards.MixedClusterClientYamlTestSuiteIT.test fails on Test Index and Search locale dependent mappings / dates #49719
Comments
Pinging @elastic/es-core-infra (:Core/Infra/Core) |
Details in elastic#49719 Relates elastic#47983
For now raised #49721 to mute the test. |
#49724 skips the tests against versions older than 6.8.5, but I think more versions need to be skipped (or other fixes are required), as this same test caused a problem when 7.x was BWC tested against 7.1.0. The failing build was https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+default-distro+bwc/BWC_VERSION=7.1.0,nodes=centos-7&&immutable/363/console One of the nodes in the cluster died with an assertion failure while running
The corresponding client side log (extracted from https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+default-distro+bwc/BWC_VERSION=7.1.0,nodes=centos-7&&immutable/363/consoleText) is:
I could not reproduce locally using:
So the problem may well depend on whether the master node is 7.1 or 7.6 and whether some request is sent direct to master or via a non-master coordinating node. |
@droberts195 you are correct, thanks for noticing this |
Failure occurred again: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+multijob-unix-compatibility/os=oraclelinux-6&&immutable/437/console Mixed cluster between 7.5.1 and 7.6.0.
Reproduce line: ./gradlew ':qa:mixed-cluster:v7.5.1#mixedClusterTest' --tests "org.elasticsearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=search/180_locale_dependent_mapping/Test Index and Search locale dependent mappings / dates}" -Dtests.seed=72298F5B38DF5C62 -Dtests.security.manager=true -Dtests.locale=sr-RS -Dtests.timezone=Europe/Kaliningrad -Dcompiler.java=12 -Druntime.java=8 |
@benwtrent I think the failure you found is unrelated to this test. This issue was specifically failing when applying cluster state without the date prefixed with |
I have extended yml's skip section to allow ranges of versions to be skipped. #50028 |
looks like the problem mentioned by @benwtrent is persisting. This test fails regularly once every day. It is always |
This failure continues to happen on a daily basis. Should we consider muting? |
Another one, same test, this time error 400, in https://gradle-enterprise.elastic.co/s/kwjlcfspzwtxe:
If I see another one today, will mute. |
Happened again
Will mute. |
From investigation in build-stats, it looks like there might be a couple of failure cases in this test. I don't know if they're the same root cause or not, but I'm going to mute this on both 7.x and 7.6 branches
|
Muting this test as it has frequent failures. See: elastic#49719
Muting this test as it has frequent failures. See: #49719
Muting this test as it has frequent failures. See: elastic#49719 Backport of: elastic#52116
I'm looking at this for the Core/Infra Team's annual issue triage. I believe we should keep this issue open and try to get around to fixing the test, since these tests are still muted in the |
This issue has had a long and complex history. It looks like there are a few different failures here - at least two I see are the original failures related to the date/time mapping, but there are also failures with We don't appear to still have any muted tests on |
Since #48703 we are seeing failures like: https://gradle-enterprise.elastic.co/s/m64s5k5k3pbn6/tests/qiq773hxdcg7e-2pri752okzdby
Failure:
So we see the difference here is an additional
8
in the date_field format.The text was updated successfully, but these errors were encountered: