On Tue, 29 Mar 2022 at 14:43, Gilles Sadowski <gillese...@gmail.com> wrote:
> Hello. > > Le mar. 29 mars 2022 à 15:23, Alex Herbert <alex.d.herb...@gmail.com> a > écrit : > > > > [...] > > > > The feature I liked from Travis was the integration of coverage reports > > from coveralls. This would red light a PR in the main page if coverage > had > > dropped. There is no coveralls GHA. I installed the Codecov action for > > [Collections] as a test a few months ago and it has been sending coverage > > emails to our dev list since. You can click through and scroll the > report. > > I do not think it red lights a PR for low coverage so you have to read > the > > report. I am undecided if I prefer the report. No-one else seems to have > > commented either way. But I think it important that any PR has automated > > checks that the new code is executed. > > IMO, it would be a regression if the move to GH has removed that feature. > +1. But flaky integration is a bigger issue. Without a CI build you cannot get the coverage failure report at all. There is a way to restart PR builds on Travis CI (e.g. if they fail spuriously due to randomness as occurs in [RNG]). But there is no way to force a link up other than waiting a few hours/days and pushing to the PR branch. Looking at Travis CI.com, it was running builds for the Geometry PR for issue 142. The last PR build was 11 days ago, and then a build on master 3 days ago when it was merged. But RNG last had a PR 6 months ago; Numbers had one 5 months ago. Travis has been building master for all recent commits. [1] https://app.travis-ci.com/github/apache/commons-geometry/pull_requests [2] https://app.travis-ci.com/github/apache/commons-rng/pull_requests [3] https://app.travis-ci.com/github/apache/commons-numbers/pull_requests
