-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] WatchAckTests testAckAllActions failure in CI #35506
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
Comments
Pinging @elastic/es-core-infra |
I've muted the test on all branches down to 6.7. A more recent failure: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/2792/console
|
Exactly the same unexpected state as in #35506 (comment) occurred in a different test,
It doesn't reproduce with:
The full exception is:
If you think there's a different root cause let me know and I'll open a separate issue for it. |
This should be fixed in master by #40658, if anyone runs across this failure let me know. I'll wait for the backport before closing this. |
A potentially related error popped up on 7.x and 7.0. Command to reproduce:
Build logs: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.0+artifactory/155/console
@gwbrown do you think this might be fixed by #40658 as well? If so, I can wait before filing another issue + muting. |
@jtibshirani I think it might be helped by that - it fits the profile for failures that would be improved by that PR. I intend to let master run for a few days to make sure it's stable with the fixed before merging the backports, so if this fails more we can mute it on 7.0/7.x and I can unmute in the backports for those branches. It doesn't look like it's failing very much, so if it doesn't fail more I'd be inclined to just wait the extra day or two. If we see failures in the tests I've unmuted on master and I have to revert, we can also go ahead and mute this. |
#40658 has been merged to all currently maintained branches after a week of running in master with no failures in this test, so I'm closing this issue. |
It seems this we have picked up a similar failure here on 7.x. Build log: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+multijob+fast+part2/3568/console Build scan: https://gradle-enterprise.elastic.co/s/ua3yon2njbyja Failure:
Reproduce with:
Can't reproduce locally. |
Note that this failure is similar to #52453, because in both cases the watch count from the watcher stats api response return an incorrect value. So perhaps the issues should merge into a single issue. I suspect that this is a broader test problem. |
I'm closing this issue in favour for #52453. |
Looking at the logs, I suspect this failure may be due to the same issue as #35503 where the watch service reloads concurrently due to new allocation ids
Build link: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.4+matrix-java-periodic/ES_BUILD_JAVA=java10,ES_RUNTIME_JAVA=java8fips,nodes=virtual&&linux/56/consoleFull
Reproduce line:
Failure:
The text was updated successfully, but these errors were encountered: