-
Notifications
You must be signed in to change notification settings - Fork 593
HDDS-3710. Merge archived jacoco coverage results #1014
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
Conversation
|
FYI @arp7 @vivekratnavel @vivekratnavel: this patch creates an XML report which can be used to upload the results to any services. @arp7 suggested updating the Sonar, we can move the sonar execution to the coverage step which can use the report |
|
Updated the sonar report. Will see how does it work after the next build on apache repo: https://github.com/apache/hadoop-ozone/actions?query=branch%3AHDDS-3710 |
vivekratnavel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 LGTM
|
Finally, it's ready to merge. You can see the results here: https://sonarcloud.io/dashboard?branch=HDDS-3710&id=hadoop-ozone (see the coverage numbers) The most tricky part: We create one big coverage report file (all it-* + unit test for all subproject), but sonar plugin requires one for each subproject. Creating one merged for each subproject (one file for each subproject which includes unit + it-*) seems to be complex, but fortunately sonar works well if the one big merged is copied to all the sub-projects. |
|
Thanks @vivekratnavel the review. I am merging it now. Sonar master will be updated with coverage data after the next full green build. |
|
@elek post-commit checks on master started failing with the error below since this PR was merged: https://github.com/apache/hadoop-ozone/runs/741621135 |
|
@adoroszlai Debugging right now. I think it's a conflict with HDDS-3627 / #975 |
|
Tried to fix with addendum, but didn't work. I will revert it and merge it back when stability is proved on a separated branch. |
|
Thanks @elek for taking care of the failure. |
…ache#1014)"" This reverts commit 322bcdd.
|
Addendum was almost good, will commit the fixed version: This is almost the same as the original one (just with fixed exclude rule to be compatible with HDDS-3627) therefore I don't think that we need an other review round. And I would prefer to push it on the weekend (It should work, but if it doesn't it can be fixed until Monday) On the fork branch it worked well: https://github.com/elek/hadoop-ozone/actions/runs/127489033 |
What changes were proposed in this pull request?
HDDS-3635 started to archive the jacoco coverage data for each of the unit and integration tests (unit, it-*).
This patch introduces a new build step to combine all of them together and archive the coverage report in HTML as a build artifact.
Notes:
acceptance test coverage is not yet included
I decided to do it only for master (branch) builds as it requires a new build which adds ~15 minutes to the full build. As the coverage data is not (yet) used for PR we don't need to enable it (yet)
We can further improve it to upload the merged data to somewhere (sonar?) Can be done in the next Jira
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3710
How was this patch tested?
I run it on my local fork. The final version expected to be here:
https://github.com/elek/hadoop-ozone/actions?query=branch%3AHDDS-3710
Download the coverage artifact and check the
index.html.