You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Kouhei Sutou (Jira)" <ji...@apache.org> on 2022/09/29 21:08:00 UTC
[jira] [Resolved] (ARROW-17550) [C++][CI] MinGW builds shouldn't compile grpcio
[ https://issues.apache.org/jira/browse/ARROW-17550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kouhei Sutou resolved ARROW-17550.
----------------------------------
Resolution: Fixed
Issue resolved by pull request 14272
[https://github.com/apache/arrow/pull/14272]
> [C++][CI] MinGW builds shouldn't compile grpcio
> -----------------------------------------------
>
> Key: ARROW-17550
> URL: https://issues.apache.org/jira/browse/ARROW-17550
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Continuous Integration
> Reporter: Antoine Pitrou
> Assignee: Kouhei Sutou
> Priority: Major
> Labels: pull-request-available
> Fix For: 10.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> MinGW builds currently compile the GCS testbench and grpcio for MinGW.
> When the compiled MinGW wheel is not in cache, compiling takes a very long time (\*). But Win32 and Win64 binary wheels are available on PyPI.
> This is pointless: the GCS testbench could simply run with the system Python instead of the msys2 Python, and always use the binaries from PyPI.
> (\*) see for example https://github.com/pitrou/arrow/runs/8071607360 where installing the GCS testbench took 18 minutes
--
This message was sent by Atlassian Jira
(v8.20.10#820010)