Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

macos-14 picking up seemingly wrong images #11574

Open
3 of 15 tasks
lukasIO opened this issue Feb 11, 2025 · 2 comments
Open
3 of 15 tasks

macos-14 picking up seemingly wrong images #11574

lukasIO opened this issue Feb 11, 2025 · 2 comments

Comments

@lukasIO
Copy link

lukasIO commented Feb 11, 2025

Description

our actions with runs-on: macos-14 and runs-on: macos-14-large started picking up unexpected runner image versions,

while it should be the latest release (20250127) it picks up this one:

Image: macos-14
  Version: 20250124.720
  Included Software: https://github.com/actions/runner-images/blob/macos-14/20250124.720/images/macos/macos-14-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/macos-14%2F20250124.720

The links to the release don't exist. And our builds are failing.
Example action run can be seen here where the first attempt (if you select it in the dropdown) passed on 20250127 and subsequent runs that I triggered manually selected the wrong version that isn't even part of the releases 🤔

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • macOS 15
  • macOS 15 Arm64
  • Windows Server 2019
  • Windows Server 2022
  • Windows Server 2025

Image version and build link

Image: macos-14
Version: 20250124.720
Included Software: https://github.com/actions/runner-images/blob/macos-14/20250124.720/images/macos/macos-14-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/macos-14%2F20250124.720

Is it regression?

Yeah, I mean it worked on 20250127 and 20250106, but also failed on 20250120 (which also isn't actually available as a release here)

Expected behavior

macos-14 should select the latest release of a runner that's available (or the one prior to that)

Actual behavior

macos-14 selects unexpected image version numbers that are not part of the releases of this repo.
this also leads to our CI breaking for non obvious reasons.

Repro steps

Source is on GH, see https://github.com/livekit/node-sdks/actions/runs/13210263418/job/36961149462 for the runs I mentioned above to inspect them. The workflow file is also available in the same repo.

@sangeeths03
Copy link

Hi @lukasIO, we will look into the issue and will keep you posted with updates.

@Hotell
Copy link

Hotell commented Feb 11, 2025

we are running into similar issues.

https://github.com/microsoft/fluentui/actions/runs/13266412882/job/37034890428#annotation:19:3

  • uses Image: macos-14-arm64 / Version: 20250124.790

https://github.com/microsoft/fluentui/actions/runs/13263445767/job/37025048276

  • uses Image: macos-14-arm64 / Version: 20250120.774

This is also resulting in non deterministic version of getting nodeJS version ( it switches between 20.18.1 and 20.18.2 )

  • not sure if this is related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants