Skip to content
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

Re-enable Watcher full cluster restart test #47950

Merged

Conversation

jakelandis
Copy link
Contributor

@jakelandis jakelandis commented Oct 11, 2019

This test is believed to be fixed by #43939

closes #40178


Note - this test was run for 24+ hours on CI hardware (for both master and 7.x) with no failures.

This test is believed to be fixed by elastic#43939

closes elastic#40178

--------

Note - this test was run for 24+ hours on CI hardware with no failures.
@jakelandis jakelandis added >test Issues or PRs that are addressing/adding tests :Data Management/Watcher v8.0.0 v7.5.0 labels Oct 11, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Watcher)

Copy link
Contributor

@andreidan andreidan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jakelandis jakelandis merged commit 63f835d into elastic:master Oct 14, 2019
@jakelandis jakelandis deleted the unmute_watcher_full_cluster_restart branch October 14, 2019 13:40
jakelandis added a commit to jakelandis/elasticsearch that referenced this pull request Oct 14, 2019
jakelandis added a commit that referenced this pull request Oct 14, 2019
jakelandis added a commit to jakelandis/elasticsearch that referenced this pull request Nov 4, 2019
…r yellow

The timeout was increased to 60s to allow this test more time to reach a
yellow state. However, the test will still on occasion fail even with the
60s timeout.

Related: elastic#48381
Related: elastic#48434
Related: elastic#47950
Related: elastic#40178
jakelandis added a commit that referenced this pull request Nov 4, 2019
The timeout was increased to 60s to allow this test more time to reach a
yellow state. However, the test will still on occasion fail even with the
60s timeout.

Related: #48381
Related: #48434
Related: #47950
Related: #40178
jakelandis added a commit to jakelandis/elasticsearch that referenced this pull request Nov 4, 2019
…tic#48848)

The timeout was increased to 60s to allow this test more time to reach a
yellow state. However, the test will still on occasion fail even with the
60s timeout.

Related: elastic#48381
Related: elastic#48434
Related: elastic#47950
Related: elastic#40178
jakelandis added a commit to jakelandis/elasticsearch that referenced this pull request Nov 4, 2019
…tic#48848)

The timeout was increased to 60s to allow this test more time to reach a
yellow state. However, the test will still on occasion fail even with the
60s timeout.

Related: elastic#48381
Related: elastic#48434
Related: elastic#47950
Related: elastic#40178
jakelandis added a commit that referenced this pull request Nov 11, 2019
The timeout was increased to 60s to allow this test more time to reach a
yellow state. However, the test will still on occasion fail even with the
60s timeout.

Related: #48381
Related: #48434
Related: #47950
Related: #40178
jakelandis added a commit that referenced this pull request Nov 11, 2019
The timeout was increased to 60s to allow this test more time to reach a
yellow state. However, the test will still on occasion fail even with the
60s timeout.

Related: #48381
Related: #48434
Related: #47950
Related: #40178
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Watcher >test Issues or PRs that are addressing/adding tests v7.5.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

FullClusterRestartIT#testWatcher failure in CI
3 participants