[core-workflow] Choosing a code coverage reporter

2016-11-22 Thread Brett Cannon
I have both Codecov and Coveralls up and running. If you have an opinion/preference, please vote at https://github.com/brettcannon/cpython-ci-test/issues/27 using the reactions on the appropriate comment (.e.g +1/-1 reaction for Codecov and/or Coveralls). Links to the code coverage results are in t

Re: [core-workflow] Choosing a code coverage reporter

2016-11-23 Thread Antoine Pitrou
On Tue, 22 Nov 2016 20:08:48 + Brett Cannon wrote: > I have both Codecov and Coveralls up and running. If you have an > opinion/preference, please vote at > https://github.com/brettcannon/cpython-ci-test/issues/27 using the > reactions on the appropriate comment (.e.g +1/-1 reaction for Codeco

Re: [core-workflow] Choosing a code coverage reporter

2016-11-23 Thread Brett Cannon
Yep, and it's a known issue. If you look at the devinabox README you will see there are complex instructions o how to work around it, but since they are theoretically brittle I didn't bother setting it up. On Wed, Nov 23, 2016, 03:36 Antoine Pitrou, wrote: > On Tue, 22 Nov 2016 20:08:48 + >

Re: [core-workflow] Choosing a code coverage reporter

2016-12-03 Thread Brett Cannon
Codecov was the clear winner among people who left a reaction on the issue and it's also my personal choice, so the code coverage reporter has been chosen! Thanks to everyone who helped out with it. On Tue, 22 Nov 2016 at 12:08 Brett Cannon wrote: > I have both Codecov and Coveralls up and runni