<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 2, 2015, at 1:58 PM, Brett Cannon <<a href="mailto:brett@python.org" class="">brett@python.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Wed, 2 Dec 2015 at 10:50 R. David Murray <<a href="mailto:rdmurray@bitdance.com" class="">rdmurray@bitdance.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, 02 Dec 2015 18:34:49 +0000, Brett Cannon <<a href="mailto:brett@python.org" target="_blank" class="">brett@python.org</a>> wrote:<br class="">
> And this bot doesn't have to do it, but we should definitely make sure we<br class="">
> have at least automated testing of all PRs on *some* OS and also a way to<br class="">
<br class="">
Kushal did some work in this direction (for unix builds), but we haven't<br class="">
done anything with it for a while.<br class=""></blockquote><div class=""><br class=""></div><div class="">Donald hooked up Travis to the GitHub test instance and runs the PRs using both gcc and clang, so I know at least GitHub + Travis has us covered. Barry has said that GitLab supports runners but you have to run them yourselves. I would also be curious to know if we could get a test coverage report somehow (e.g., can <a href="http://coveralls.io/" class="">coveralls.io</a> support be added and have it use <a href="https://bitbucket.org/ned/coveragepy/src/787158b1da024fd57b9a4f05c35042b7cdbe74a1/coverage/fullcoverage/encodings.py" class="">https://bitbucket.org/ned/coveragepy/src/787158b1da024fd57b9a4f05c35042b7cdbe74a1/coverage/fullcoverage/encodings.py</a> which requires a checkout of coverage.py).</div></div></div></div></blockquote><div><br class=""></div><div>I tried to setup coverage reports via <a href="https://codecov.io" class="">https://codecov.io</a> but I didn’t know how to make it work with CPython. It looked like there was some support in the Makefile but that didn’t seem to work out so well. It also supports C coverage too but I’ve never used it.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_quote"><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="">
> verify the PR contributor signed the CLA (the testing should be easy enough<br class="">
> on either and the CLA should be doable somehow).<br class="">
<br class="">
This should be easy enough to do via the xmlrpc interface to the tracker, or<br class="">
(better) the rest interface if/when it lands.<br class=""></blockquote><div class=""><br class=""></div><div class="">I guess it would simply require people to add their GitHub IDs to their issue tracker profile. We probably should also make sure the process gets as automated as possible as I think Ewa still flips some bits manually.</div></div></div></div></blockquote><div><br class=""></div><div>With a tiny little shim server, you’d be able to make a status check that shows whether or not a PR is covered by the CLA or not. It’d be similar to Travis except instead of checking out the code and running tests, it’d just check for CLA status and report back.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_quote"><div class=""><br class=""></div><div class="">-Brett</div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="">
--David<br class="">
_______________________________________________<br class="">
core-workflow mailing list<br class="">
<a href="mailto:core-workflow@python.org" target="_blank" class="">core-workflow@python.org</a><br class="">
<a href="https://mail.python.org/mailman/listinfo/core-workflow" rel="noreferrer" target="_blank" class="">https://mail.python.org/mailman/listinfo/core-workflow</a><br class="">
This list is governed by the PSF Code of Conduct: <a href="https://www.python.org/psf/codeofconduct" rel="noreferrer" target="_blank" class="">https://www.python.org/psf/codeofconduct</a><br class="">
</blockquote></div></div>
_______________________________________________<br class="">core-workflow mailing list<br class=""><a href="mailto:core-workflow@python.org" class="">core-workflow@python.org</a><br class="">https://mail.python.org/mailman/listinfo/core-workflow<br class="">This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct</div></blockquote></div><br class=""><div class="">
<br class="">-----------------<br class="">Donald Stufft<br class="">PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
</div>
<br class=""></body></html>