Skip to content

FullClusterRestartIT#testWatcher failure in CI #40178

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.

Sign up for GitHub

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

Jump to bottom
Closed
jaymode opened this issue Mar 18, 2019 · 2 comments · Fixed by #47950
Closed

FullClusterRestartIT#testWatcher failure in CI #40178

jaymode opened this issue Mar 18, 2019 · 2 comments · Fixed by #47950
Labels
:Data Management/Watcher >test-failure Triaged test failures from CI

Comments

@jaymode
Copy link
Member

jaymode commented Mar 18, 2019

The testWatcher test in the FullClusterRestartIT class failed in CI, https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/2595/console. This did not reproduce for me.

Reproduce line:

./gradlew :x-pack:qa:full-cluster-restart:without-system-key:v7.0.0#upgradedClusterTestRunner \
  -Dtests.seed=B937D3C214B32CC5 \
  -Dtests.class=org.elasticsearch.xpack.restart.FullClusterRestartIT \
  -Dtests.method="testWatcher" \
  -Dtests.security.manager=true \
  -Dtests.locale=ar-TN \
  -Dtests.timezone=America/Swift_Current \
  -Dcompiler.java=11 \
  -Druntime.java=8

Error:

java.lang.AssertionError: 
Expected: <2>
     but: was <3>
	at __randomizedtesting.SeedInfo.seed([B937D3C214B32CC5:D4DA200FE4D2BB33]:0)
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
	at org.junit.Assert.assertThat(Assert.java:956)
	at org.junit.Assert.assertThat(Assert.java:923)
	at org.elasticsearch.xpack.restart.FullClusterRestartIT.assertBasicWatchInteractions(FullClusterRestartIT.java:369)
	at org.elasticsearch.xpack.restart.FullClusterRestartIT.testWatcher(FullClusterRestartIT.java:186)

It looks like the test depends on versioning, but something else updates the watch between creation and the update; maybe execution of the watch?
@jaymode jaymode added >test-failure Triaged test failures from CI :Data Management/Watcher labels Mar 18, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@jaymode
Copy link
Member Author

jaymode commented Mar 18, 2019 •
edited
Loading

Muted on master, 7.x, and 7.0.

jakelandis added a commit to jakelandis/elasticsearch that referenced this issue Oct 11, 2019
@jakelandis
Re-enable Watcher full cluster restart test
0949bd3 
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 mentioned this issue Oct 11, 2019
Merged
jakelandis added a commit that referenced this issue Oct 14, 2019
@jakelandis
Re-enable Watcher full cluster restart test (#47950)
63f835d 
This test is believed to be fixed by #43939

closes #40178
jakelandis added a commit to jakelandis/elasticsearch that referenced this issue Oct 14, 2019
@jakelandis
Re-enable Watcher full cluster restart test (elastic#47950)
f13b6a2 
This test is believed to be fixed by elastic#43939

closes elastic#40178
@jakelandis jakelandis mentioned this issue Oct 14, 2019
Merged
jakelandis added a commit that referenced this issue Oct 14, 2019
@jakelandis
Re-enable Watcher full cluster restart test (#47950) (#48000)
5a4745a 
This test is believed to be fixed by #43939

closes #40178
jakelandis added a commit to jakelandis/elasticsearch that referenced this issue Nov 4, 2019
@jakelandis
Mute FullClusterRestartTest#testWatcher and bring back 30s timeout fo…
c24be73 
…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 jakelandis mentioned this issue Nov 4, 2019
Merged
jakelandis added a commit that referenced this issue Nov 4, 2019
@jakelandis
Mute FullClusterRestartTest#testWatcher and 30s timeout for ye… (#48848)
3aa44e4 
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 issue Nov 4, 2019
@jakelandis
Mute FullClusterRestartTest#testWatcher and 30s timeout for ye… (elas…
c11085e 
…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 issue Nov 4, 2019
@jakelandis
Mute FullClusterRestartTest#testWatcher and 30s timeout for ye… (elas…
5ebe967 
…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 issue Nov 11, 2019
@jakelandis
[7.x] Mute FullClusterRestartTest#testWatcher and 30s timeout… (#48850)
909fbd0 
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 issue Nov 11, 2019
@jakelandis
[7.5] Mute FullClusterRestartTest#testWatcher and 30s timeout… (#48851)
b810048 
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
Assignees
No one assigned
Labels
:Data Management/Watcher >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Re-enable Watcher full cluster restart test jakelandis/elasticsearch
2 participants
@jaymode @elasticmachine