rmuir opened a new issue, #11839:
URL: https://github.com/apache/lucene/issues/11839

   ### Description
   
   Currently, when running the build (e.g. `gradlew coverage`) you get a 
per-module report.
   
   Ideally we'd produce an aggregate report (similar to what black magic 
jenkins is doing: 
https://ci-builds.apache.org/job/Lucene/job/Lucene-Coverage-main/lastSuccessfulBuild/jacoco/
   
   It would be great to also print the summary to the console (same as #11837). 
   
   This would be nice, a single artifact of the code coverage for a build. For 
example, It could eventually be archived as a github action to help us better 
inspect PRs.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to