You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Antoine Pitrou (Jira)" <ji...@apache.org> on 2022/06/15 13:42:00 UTC
[jira] [Updated] (ARROW-16835) [CI][Python] Investigate using self-hosted runner for older macOS wheels
[ https://issues.apache.org/jira/browse/ARROW-16835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Pitrou updated ARROW-16835:
-----------------------------------
Description:
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.
was:
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.
> [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)