Skip to content
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

Closed
tlfeng opened this issue Apr 12, 2022 · 5 comments
Closed

[BUG] Test failure exists but Gradle 'check' task passes #2878

tlfeng opened this issue Apr 12, 2022 · 5 comments
Labels
bug Something isn't working Priority-High :test Adding or fixing a test

Comments

@tlfeng
Copy link
Collaborator

tlfeng commented Apr 12, 2022

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:

Maybe the kind of tests is not critical, so that it's not failing the build.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
If not to fail the Gradle check task is by design, then keep it as it is. Otherwise, fail the check 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.

@owaiskazi19
Copy link
Member

@tlfeng can we close this issue?

@tlfeng
Copy link
Collaborator Author

tlfeng commented Apr 13, 2022

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).

@dreamer-89
Copy link
Member

This issue can result in failure to identify changes, which actually break backword compatibility. Thus, adding high-priority label.

@andrross
Copy link
Member

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.

@dblock
Copy link
Member

dblock commented Nov 15, 2022

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.

@dblock dblock closed this as completed Nov 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Priority-High :test Adding or fixing a test
Projects
None yet
Development

No branches or pull requests

5 participants