-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Gradle task componentTests should not stop entirely when only one task fails #12900
Comments
Good First Issue - Notes for Contributors Please note that we allow only one We do not assign issues to contributors. If you would like to pick up this issue, do post a comment below to express your interest and check if there is anyone else who is already working on the issue. We will do our best to reply and give you the go-ahead, but if we don't, feel free to submit a PR as long as there is no one else working on it. To get started, do read through our contributing guidelines carefully, and set up a development environment on your local machine before making a PR. If you need any clarifications on our developer guide, or are facing issues that are not found in our troubleshooting guide, please post a message in our discussion forum. |
Hi, me and my classmate @jckras want to contribute to our first open-source project. Can we resolve this issue? |
Sure @Hkovin, feel free to open a PR for this issue |
Hi, my partner and I need to work on an issue with different requirements so we can no longer work on this one. Thank you though! |
Hello, can I work on this issue? |
@emrekenar Hi! Thank you for your interest in the project. Since there is nobody currently working on this, you are free to submit a PR for this. |
The Gradle task
componentTests
now depends on the two Gradle tasksunitTests
, andintegrationTests
since #12056. These can be independent from each other, so if one fails, we should continue to execute the other (except when it fails due to the failure of a common dependency, like compilation). However, when either of them fails due to a failing test, the other one is not completed because the execution of the wholecomponentTests
task is aborted.To prevent this, we can run
componentTests
with the option--continue
, just like the Gradle tasklint
. This probably needs to be changed in the GitHub workflows and in the documentation.The text was updated successfully, but these errors were encountered: