[jira] [Commented] (ARROW-16835) [CI][Python] Investigate using self-hosted runner for older macOS wheels

["Antoine Pitrou (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARROW-16835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554608#comment-17554608 ] 

Antoine Pitrou commented on ARROW-16835:
----------------------------------------

[~assignUser]  Does this sound reasonable?

> [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.7#820007)