<div dir="ltr">I like the current structure of the make check rule which has in increasing number of sub-targets (pep8, pyflakes, tests, etc) so it is still easy to run individual targets if the check rule is more than you need. For me adding this is a big +1.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 15, 2017 at 12:04 PM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Mon, May 15, 2017 at 4:47 PM, Fred Rolland <<a href="mailto:frolland@redhat.com">frolland@redhat.com</a>> wrote:<br>
> Hi,<br>
><br>
> We are introducing Pylint to be performed as part of the 'check' target.<br>
> Once that patch [1] will be merged, every execution of 'make check' will<br>
> include also a Pylint analysis.<br>
><br>
> Note that execution time will be longer by about 2 minutes.<br>
><br>
> However, you are can use 'jobs' flag to tell 'make' to execute recipes<br>
> simultaneously.<br>
> Be aware that the output of the jobs will be interleaved.<br>
><br>
> For example, running 'make' with two parallel jobs:<br>
><br>
> make --jobs=2 check<br>
><br>
> Regards,<br>
> Freddy<br>
><br>
> [1] <a href="https://gerrit.ovirt.org/#/c/76390/" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/#/c/<wbr>76390/</a><br>
<br>
</div></div>I'm a not as frequent user of `make check` as I used to be, but I'm<br>
cool with this addition. I'd like to hear if others are bothered.<br>
<span class="HOEnZb"><font color="#888888"><br>
Dan.<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Adam Litke</div></div>
</div>