-
Notifications
You must be signed in to change notification settings - Fork 25k
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] HistoryTemplateIndexActionMappingsTests.testIndexActionFields is failing #65091
Labels
:Data Management/Watcher
Team:Data Management
Meta label for data/management team
>test-failure
Triaged test failures from CI
Comments
valeriy42
added
>test-failure
Triaged test failures from CI
:Data Management/Watcher
labels
Nov 16, 2020
elasticmachine
added
the
Team:Data Management
Meta label for data/management team
label
Nov 16, 2020
Pinging @elastic/es-core-features (Team:Core/Features) |
valeriy42
added a commit
that referenced
this issue
Nov 17, 2020
probakowski
added a commit
that referenced
this issue
Nov 18, 2020
When we trigger watcher in tests we may fail if scheduler is paused. That can happen when watcher is reloading due to changes in its shards. This is transient state and retry should fix it. This change adds assertBusy around triggering code so we will try again. Closes #65183 #65176 #65117 #65091 #65089 #65086 #65064 #65063
Should be fixed by #65186 |
jaymode
added a commit
to jaymode/elasticsearch
that referenced
this issue
Dec 3, 2020
HistoryTemplateIndexActionMappingsTests testIndexActionFields has been failing in CI. This commit mutes the test. Relates elastic#65091
jaymode
added a commit
that referenced
this issue
Dec 3, 2020
HistoryTemplateIndexActionMappingsTests testIndexActionFields has been failing in CI. This commit mutes the test. Relates #65091
probakowski
added a commit
that referenced
this issue
Jan 13, 2021
When watcher gets reloaded (due to shards routings change) during tests we sometimes get additional watcher history entry (either that the same watch is already queued or that it got throttled because it tried to execute right after previous one). That trips our assertions which expect exact number of entries. This change relaxes them to allow exactly-one-more situation and leaves all other checks in place. Closes #65831 Closes #65176 Closes #65064 Closes #65091
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
Build scan: https://gradle-enterprise.elastic.co/s/r4r5gsjm4daqg
Repro line:
Reproduces locally?: No
Applicable branches: master
Failure history: build stats failed 7 times in the last 7 days
Failure excerpt:
The text was updated successfully, but these errors were encountered: