-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[BUG] ClusterRerouteIT.testDelayWithALargeAmountOfShards (random test failure) #1561
Comments
Add more information: https://ci.opensearch.org/logs/ci/workflow/OpenSearch_CI/PR_Checks/Gradle_Check/gradle_check_992.log
|
Getting suite timeout exceeded (>= 1200000 msec) after runnings tests in isolation for 100 times
|
@owaiskazi19 : With 1200000ms (20 mins), each test is getting 12 sec to finish which is very less. If you want to run this in continuation, suggest you to change the timeout to a higher value. Agree this is problematic as test timeout should consider the iteration count as well and should have 100 * 120000 ms as total run timeout. |
Increasing the test timeout to 30 mins worked. Thanks @dreamer-89 for the input.
|
This flaky test still exists, see the latest failed test: https://build.ci.opensearch.org/job/gradle-check/35560/testReport/junit/org.opensearch.cluster.allocation/ClusterRerouteIT/testDelayWithALargeAmountOfShards/. |
Tracked by autocut: #14298 |
Describe the bug
Random test failure. :( Please dig in and figure out what went wrong :(
https://ci.opensearch.org/logs/ci/workflow/OpenSearch_CI/PR_Checks/Gradle_Check/gradle_check_992_reports.zip
The text was updated successfully, but these errors were encountered: