-
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] WatcherUtilsTests testSerializeSearchRequest failing #78035
Labels
:Data Management/Watcher
Team:Data Management
Meta label for data/management team
>test-failure
Triaged test failures from CI
Comments
Pinging @elastic/es-data-management (Team:Data Management) |
This reproduces locally for me:
running against 8d3f781
|
The deserialize test is also failing (
I'm going to mute both tests methods on master. |
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
Sep 21, 2021
elasticsearchmachine
pushed a commit
that referenced
this issue
Sep 21, 2021
This my fault and related to #77479. Unfortunately local and pr ci test runs didn't catch this... |
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Sep 21, 2021
The check was an identity check between the default constant and the set indices options. This check is incorrect because in many cases when `IndicesOptions` is parsed or randomly generated in tests, then this check incorrectly returns false when in fact an `IndicesOptions` instance is equal to the default constant, but it is just a different instance/object. Closes elastic#78035
martijnvg
added a commit
that referenced
this issue
Sep 22, 2021
…78070) The check was an identity check between the default constant and the set indices options. This check is incorrect because in many cases when `IndicesOptions` is parsed or randomly generated in tests, then this check incorrectly returns false when in fact an `IndicesOptions` instance is equal to the default constant, but it is just a different instance/object. Closes #78035
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Sep 22, 2021
Backporting elastic#78070 to 7.x branch. The check was an identity check between the default constant and the set indices options. This check is incorrect because in many cases when `IndicesOptions` is parsed or randomly generated in tests, then this check incorrectly returns false when in fact an `IndicesOptions` instance is equal to the default constant, but it is just a different instance/object. Closes elastic#78035
elasticsearchmachine
pushed a commit
that referenced
this issue
Sep 22, 2021
…78165) Backporting #78070 to 7.x branch. The check was an identity check between the default constant and the set indices options. This check is incorrect because in many cases when `IndicesOptions` is parsed or randomly generated in tests, then this check incorrectly returns false when in fact an `IndicesOptions` instance is equal to the default constant, but it is just a different instance/object. Closes #78035
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Data Management/Watcher
Team:Data Management
Meta label for data/management team
>test-failure
Triaged test failures from CI
Didn't reproduce but this has failed 12 times in the past week so I think there's definitely something up. Looks to be specific to
master
Build scan:
https://gradle-enterprise.elastic.co/s/5xlsqazi26hns/tests/:x-pack:plugin:watcher:test/org.elasticsearch.xpack.watcher.support.WatcherUtilsTests/testSerializeSearchRequest
Reproduction line:
./gradlew ':x-pack:plugin:watcher:test' --tests "org.elasticsearch.xpack.watcher.support.WatcherUtilsTests.testSerializeSearchRequest" -Dtests.seed=77B8557950BD0018 -Dtests.locale=ar-SA -Dtests.timezone=Antarctica/McMurdo -Druntime.java=11
Applicable branches:
master
Reproduces locally?:
No
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.xpack.watcher.support.WatcherUtilsTests&tests.test=testSerializeSearchRequest
Failure excerpt:
The text was updated successfully, but these errors were encountered: