[
https://issues.apache.org/jira/browse/ARROW-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17660283#comment-17660283
]
Rok Mihevc commented on ARROW-3260:
-----------------------------------
This issue has been migrated to [issue
#19600|https://github.com/apache/arrow/issues/19600] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> [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: 0.5h
> 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
(v8.20.10#820010)
