HDDS-10056. Silent failure in unit check#5913
Merged
adoroszlai merged 2 commits intoapache:masterfrom Jan 3, 2024
Merged
Conversation
sadanand48
approved these changes
Jan 3, 2024
Contributor
sadanand48
left a comment
There was a problem hiding this comment.
Thanks for the patch @adoroszlai , LGTM.
Contributor
Author
|
Thanks a lot @sadanand48 for the review. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
HDDS-10013 removed dependency on
junitfrom modules which do not have tests. Nowunitcheck finishes with success in 1 minute instead of running unit tests:This change adds
maven.test.skip=truein such modules to prevent the problem.It also tweaks
junit.sh(run byunitcheck) to look for errors other than test failures in Maven output to avoid silent failure of the check.https://issues.apache.org/jira/browse/HDDS-10056
How was this patch tested?
Ran
unitcheck locally (restricted to a single test for quick results):Also verified that the fix in
junit.shwithout the POM changes catches the failure:CI:
https://github.com/adoroszlai/ozone/actions/runs/7395145245/job/20117969381