[
https://issues.apache.org/jira/browse/ARROW-16835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571869#comment-17571869
]
Jacob Wujciak-Jens commented on ARROW-16835:
--------------------------------------------
With the new capacity of crossbow this is no longer necessary. But I would like
to know if it is really necessary that we build on(or rather for) 10.9 & 10.13
which have been EOL for 5/~2 years both are not available as github runners and
even 10.15 will be deprecated soon, so there is no easy way to build/test on
these other than setting the deployment target.
> [CI][Python] Investigate using self-hosted runner for older macOS wheels
> ------------------------------------------------------------------------
>
> Key: ARROW-16835
> URL: https://issues.apache.org/jira/browse/ARROW-16835
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Continuous Integration, Packaging, Python
> Reporter: Antoine Pitrou
> Priority: Major
>
> Currently the {{wheel-macos-high-sierra-\*}} and {{wheel-macos-mavericks-\*}}
> packages use Github Actions runners in order to get the right macOS version.
> But perhaps that could be improved by making it a two-step process?
> - the expensive step, which is building the wheel, can be done on a newer
> macOS version if the right macOS Deployment Target is set
> - the cheaper step, which is testing the just-built wheel, can be run on the
> desired macOS runner
> That way, the very constrained execution capacity available on GHA macOS
> runners would be less stressed by our CI jobs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
