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

Posted to issues@arrow.apache.org by "Antoine Pitrou (JIRA)" <ji...@apache.org> on 2018/10/25 07:27:00 UTC

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

     [ https://issues.apache.org/jira/browse/ARROW-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antoine Pitrou resolved ARROW-3260.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.12.0

Issue resolved by pull request 2831
[https://github.com/apache/arrow/pull/2831]

> [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
>            Assignee: Antoine Pitrou
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.12.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)