-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Increase assertAllCancellableTasksAreCancelled timeout #89744
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
Increase assertAllCancellableTasksAreCancelled timeout #89744
Conversation
Pinging @elastic/es-distributed (Team:Distributed) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, assuming CI passes. Hope it was just the timeout the reason for the failures! 🤞
Thanks @kingherc. Do you know actually if backporting to 8.3 is necessary here? I have the impression that since main is now 8.5, only the CI for 8.4 will be periodically running, and there is no more 8.3 changes. |
@pxsalehi seeing the release schedule, I believe 8.3 may not be necessary. But feel free to check with the team as well to be certain. |
Yes, I thought the same. I think I'll take out the 8.3. Thanks. |
@elasticmachine update branch |
💔 Backport failed
You can use sqren/backport to manually backport by running |
The following two failures happen rarely, but both fail in the same `assertBusy` block. I don't have a clue why, and couldn't reproduce them. Considering the amount of checks in that block, maybe a larger timeout is more suitable. (Also it seems from the test history, it is not uncommon for those tests to take 2-3s, so every few thousand runs hitting the 10s timeout seems likely, IMO!) Relates elastic#88884, elastic#88201
The following two failures happen rarely, but both fail in the same `assertBusy` block. I don't have a clue why, and couldn't reproduce them. Considering the amount of checks in that block, maybe a larger timeout is more suitable. (Also it seems from the test history, it is not uncommon for those tests to take 2-3s, so every few thousand runs hitting the 10s timeout seems likely, IMO!) Relates #88884, #88201
The following two failures happen rarely, but both fail in the same `assertBusy` block. I don't have a clue why, and couldn't reproduce them. Considering the amount of checks in that block, maybe a larger timeout is more suitable. (Also it seems from the test history, it is not uncommon for those tests to take 2-3s, so every few thousand runs hitting the 10s timeout seems likely, IMO!) Relates elastic#88884, elastic#88201
The following two failures happen rarely, but both fail in the same
assertBusy
block. I don't have a clue why, and couldn't reproduce them. Considering the amount of checks in that block, maybe a larger timeout is more suitable. (Also it seems from the test history, it is not uncommon for those tests to take 2-3s, so every few thousand runs hitting the 10s timeout seems likely, IMO!)Relates #88884, #88201