You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Krisztian Szucs (JIRA)" <ji...@apache.org> on 2018/09/18 10:48:00 UTC

[jira] [Comment Edited] (ARROW-3260) [CI] Make linting a separate job

    [ https://issues.apache.org/jira/browse/ARROW-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618907#comment-16618907 ] 

Krisztian Szucs edited comment on ARROW-3260 at 9/18/18 10:47 AM:
------------------------------------------------------------------

It's indeed orthogonal, however in order to not increase the CI runtimes We should run all of the linters in a single CI step.


was (Author: kszucs):
It's indeed orthogonal :) 

> [CI] Make linting a separate job
> --------------------------------
>
>                 Key: ARROW-3260
>                 URL: https://issues.apache.org/jira/browse/ARROW-3260
>             Project: Apache Arrow
>          Issue Type: Wish
>          Components: C++, Continuous Integration, Python
>            Reporter: Antoine Pitrou
>            Priority: Major
>
> When pushing changes I get routinely frustrated because Travis-CI fails early on a linting failure. It would be nice if linting (Python, C++) was a separate job so as not to disrupt the development workflow so much.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)