btw, you can look at the current reports created by jenkins here: https://ci-builds.apache.org/job/Lucene/job/Lucene-Coverage-main/lastBuild/jacoco/
On Tue, Oct 4, 2022 at 6:51 AM Robert Muir <rcm...@gmail.com> wrote: > > we can run the tests with coverage option and produce coverage graph > from the github actions, but need to look at the docs to see where to > put it so it will be available. > > I want us to be careful about the word "check" as I'm adamantly > against any such automated check (e.g. coverage > N%) in the logic. > Coverage report is just a tool to help us and the moment we do stupid > shit like that, is the moment people start gaming it just to make the > build pass. > > On Mon, Oct 3, 2022 at 10:57 PM Patrick Zhai <zhai7...@gmail.com> wrote: > > > > Hi folks, > > I'm not sure whether people have already discussed this but I'm wondering > > whether we want to add a workflow that pulls out the code coverage whenever > > a PR was created? It should be easier for both the reviewers and the > > contributors to figure out what can be improved, or at least figure out a > > part that is probably not covered by the tests? > > > > Best > > Patrick --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
