[jira] [Resolved] (ARROW-16793) [CI] Update tags for M1 self-hosted runner jobs to be more specific

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

     [ https://issues.apache.org/jira/browse/ARROW-16793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antoine Pitrou resolved ARROW-16793.
------------------------------------
    Fix Version/s: 9.0.0
       Resolution: Fixed

Issue resolved by pull request 13350
[https://github.com/apache/arrow/pull/13350]

> [CI] Update tags for M1 self-hosted runner jobs to be more specific
> -------------------------------------------------------------------
>
>                 Key: ARROW-16793
>                 URL: https://issues.apache.org/jira/browse/ARROW-16793
>             Project: Apache Arrow
>          Issue Type: Task
>          Components: Continuous Integration
>            Reporter: Raúl Cumplido
>            Assignee: Raúl Cumplido
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 9.0.0
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> We have tried to add a new self-hosted runner at crossbow which is not an M1. The problem is that some of the M1 jobs where scheduled on this node because we are only tagging them with `runs-on: self-hosted`. The idea of this PR is to be a little more specific and tag them also with the OS and architecture as defined on github guidelines:
> [https://docs.github.com/en/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow]
> An example of a job that failed and was scheduled to a Linux k8s node is here:
> [https://github.com/ursacomputing/crossbow/runs/6789533822?check_suite_focus=true]
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)