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/02/17 15:15:00 UTC

[jira] [Resolved] (ARROW-15682) [CI] Github starting to migrate "windows-latest" tag from windows 2019 to windows 2022

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

Antoine Pitrou resolved ARROW-15682.
------------------------------------
    Fix Version/s: 8.0.0
       Resolution: Fixed

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

> [CI] Github starting to migrate "windows-latest" tag from windows 2019 to windows 2022
> --------------------------------------------------------------------------------------
>
>                 Key: ARROW-15682
>                 URL: https://issues.apache.org/jira/browse/ARROW-15682
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Continuous Integration
>            Reporter: Weston Pace
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 8.0.0
>
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> Announcement: https://github.blog/changelog/2022-01-11-github-actions-jobs-running-on-windows-latest-are-now-running-on-windows-server-2022/
> It will be rolling out over the next 8 weeks.  I noticed because they changed one of the runners for my local fork.
> Some of our builds assume windows-latest means 2019.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)