-
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] Test failure exists but Gradle 'check' task passes #2878
Comments
@tlfeng can we close this issue? |
Hi @owaiskazi19, before closing the issue, I would like to find out the code or the reason that not to fail the Gradle build when test failure occurs in these kinds of tests (YAML REST API test and High-Level-Rest-Client test). |
This issue can result in failure to identify changes, which actually break backword compatibility. Thus, adding |
This is actually the desired behavior that was added in #2547 The idea is to do limited retries with the same seed. If it passes on a retry then it is a flaky test, but we don't necessarily want to fail the build in such a case. |
I think this is working as expected. I'm closing this, reopen if you can show an example where all retries failed and we still reported success. |
Describe the bug
The Gradle
check
task may pass, even if test failure occurred.I'm not sure if this is by design, not to fail the task in the following scenario:
example: Add request parameter 'cluster_manager_timeout' and deprecate 'master_timeout' - in Index APIs except index template APIs #2660 (comment)
example: Add request parameter 'cluster_manager_timeout' and deprecate 'master_timeout' - in Index Template APIs #2678 (comment) and Added a new line linter #2875 (comment)
Maybe the kind of tests is not critical, so that it's not failing the build.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If not to fail the Gradle
check
task is by design, then keep it as it is. Otherwise, fail thecheck
task when there are test failures in the above situation.Plugins
none.
Screenshots
none.
Host/Environment (please complete the following information):
n/a
Additional context
none.
The text was updated successfully, but these errors were encountered: