[
https://issues.apache.org/jira/browse/ARROW-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16697192#comment-16697192
]
Wes McKinney commented on ARROW-2858:
-------------------------------------
I think it'd be OK to try to mock as much of the network-depending code as
possible. The goal really is to test that the business logic works
> Of course it depends on how do We want to move forward with the build system
I think there's value in being able to run jobs on public CI systems, the
approach used for build orchestration and management need not conflict with
that. The only thing we cannot do is nothing =) The lack of a more scalable
testing and monitoring solution is becoming a drag on the project, so we need
to discuss on the mailing list and come up with a plan.
There are some things we just can't do in public CI services. Example: testing
on GPUs. Because we can't run certain tests on public CIs doesn't mean that
public CIs are useless. We have to get creative with our approach
> [Packaging] Add unit tests for crossbow
> ---------------------------------------
>
> Key: ARROW-2858
> URL: https://issues.apache.org/jira/browse/ARROW-2858
> Project: Apache Arrow
> Issue Type: Task
> Components: Packaging
> Reporter: Phillip Cloud
> Priority: Major
> Fix For: 0.13.0
>
>
> As this code grows we should start adding unit tests to make sure we can make
> changes safely.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
