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

[junit-platform] Report total failure count, not just test failures #4176

Merged
merged 1 commit into from
Jun 21, 2020

Conversation

kriegfrj
Copy link
Contributor

This is necessary as Jupiter reports container failures separately from the children if the container fails before the children are executed.

Fixes #4175.

This is necessary as Jupiter reports container failures separately
from the children if the container fails before the children are
executed.

Fixes bndtools#4175.

Signed-off-by: Fr Jeremy Krieg <[email protected]>
@bjhargrave bjhargrave merged commit c009a67 into bndtools:master Jun 21, 2020
@bjhargrave
Copy link
Member

Thanks!

@kriegfrj kriegfrj deleted the 4175-container-failures branch June 21, 2020 22:08
@bjhargrave bjhargrave added the maint-candidate Issues or pull requests that are candidates for a maintenance release label Jun 29, 2020
@bjhargrave bjhargrave added this to the 5.2 milestone Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maint-candidate Issues or pull requests that are candidates for a maintenance release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[junit-platform] Container failures don't cause Gradle failure
2 participants