Why does my workflow keep timing out waiting for a runner? #171845
Replies: 2 comments
-
If you’re using something like runs-on: ubuntu-latest That should pick up a GitHub-hosted runner without issue. But if you’re using a custom label, then you must have a self-hosted runner registered and online. If none is online, the job will just queue forever. |
Beta Was this translation helpful? Give feedback.
-
That works, thanks. I think I accidentally combined the ubuntu runner names with the macos runners. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Question
What GitHub Actions topic or product is this about?
Misc
Discussion Details
I spent a couple of days putting together and debugging a workflow for building my project. One of the workflows was for a linux build, and earlier in the development process I was able to run it. However, the last few times I've tried to run it, it gets timed out for exceeding the maximum execution time. The thing is, this is happening because no runner picks it up in the first place. It just gets queued and then times out 24 hours later.
https://github.com/blackears/parrotLipsync/actions/runs/17351717284
I'd like to have this run, since i think it is debugged now and would like to create a linux build. How do I get this workflow to get picked up?
Beta Was this translation helpful? Give feedback.
All reactions