Using “Requested labels: windows-11-arm64” and then it’s endless waiting for “Waiting for a runner to pick up this job...” #159390
Replies: 2 comments
-
| Sounds like the runner just needs a little more time or a manual restart sometimes those preview ARM64 Windows runners can be flaky. Meanwhile, I’d GET PETTIN my cat and hope it clears up! | 
Beta Was this translation helpful? Give feedback.
-
| 🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as  2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the  Thank you for helping bring this Discussion to a resolution! 💬 | 
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Hi there, I begin my workflow file with this: name: build-arm64
on:
workflow_dispatch:
jobs:
build-windows-arm64:
# Use native Windows ARM64 runner
runs-on: windows-11-arm64
defaults:
run:
shell: msys2 {0}
But unfortunately, it got stuck at “Waiting for a runner to pick up this job...” for more than eight hours. I do check the documentation, and it seems that ARM64 Windows instances are already available, though in preview mode? Is there any bug or policy change related to ARM64 here, if I may know?
Beta Was this translation helpful? Give feedback.
All reactions