Pull request workflow stuck in Queued status for 12 hours #22505
-
I have set up a new private repository in my organisation (on a free plan) and tried to commit initial PR workflow. I have submitted the changes through a PR to verify that the workflow is working, but it’s been stuck in Queued state for over 12 hours now. I tried restarting, but it did nothing. I’m not out of minutes, I barely make a dent in the 2000 minutes budget (70 minutes used this month). The workflow I was trying to add was just supposed to run npm test:
I thought that maybe the workflow file was malformed, or one of the steps was wrong, but even in that case I would expect some error message. When I try searching online, these kinds of problems happen due to outages, but GitHub Status doesn’t mention any problems with Actions. Not sure what to do about this. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
For anyone who stumbles upon this post in the future with the same problem as I had: I suspect the problem was the Still, an error message would be nice. |
Beta Was this translation helpful? Give feedback.
For anyone who stumbles upon this post in the future with the same problem as I had: I suspect the problem was the
runs-on: ubuntu latest
line, which should instead have a hyphen between “ubuntu” and “latest”. Workflow was probably stuck waiting for a runner with a type that doesn’t exist.Still, an error message would be nice.