-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
testWatcherRestart occasionally fails in REST tests #33753
Comments
Pinging @elastic/es-core-infra |
Looking at the failure output in the original comment, we see that on one node (node id Line 183 in 230cd10
we'd actually need to ensure that all watches are started? @spinscale / @hub-cap can one of you please have a look at this one? |
Occurred again https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+multijob-unix-compatibility/os=debian/58/console
|
And another one:
|
I start to think we should mute this, especially since there seems to be a PR on the way to fix: #35243 |
And another one. This should definitely be muted IMHO: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+bwc-tests/96/console |
I muted this on 6.x with c847953 and on 6.5 with 15632d7. I haven't seen any failures on master since this seems to be a bwc thing, also there are three other similarly named |
There was a failure on 6.x for this test today: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+intake/926/console @pgomulka - Is this still an issue? |
Reverted in 633aac1 |
I am closing this issue since this specific test upgrading TO 6.x, and as such was removed from 7.x (a long time ago). The test is currently muted in 6.x (non-existent in 7+) and I don't believe it worth effort to track down a possible root cause of the flakey-ness of this test since 7.0 has been released and we haven't had real world issues w/r/t Watcher and upgrading TO 6.x. |
I count 10 failures of
WatchBackwardsCompatibilityIT#testWatcherRestart
since June 13th, all in the 6.x series (i.e. 6.2, 6.3 or 6.4 as well as 6.x). They are not all the same as the failure described here, but some of them are. The latest one was in a BWC test but non-BWC tests also failed in this fashion.The build link is https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.4+bwc-tests/1/console
The reproduction line follows, but does not reproduce for me:
The output follows.
The text was updated successfully, but these errors were encountered: