all github actions are stucked and can not execute
See original GitHub issuehi there, recently I found that the github action in shardingsphere has something wrong. as we can see, there is only one action is in progress
but the other 12 actions are queued
status and pending resource to execute.
Issue Analytics
- State:
- Created a year ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Github action stuck at queue #26693
Github action stuck at queue. ... I can't even cancel the flow. ... They had to manually clear out the stuck run, everything...
Read more >all github action jobs are queued and never running
Following the incident with GitHub Actions on February 5, it appears that, even at present, it is not functioning properly with various ...
Read more >[GitHub Support] - Jobs stuck in queue for hours
All I do know is that like this, I cannot work, ... I can see a number of jobs executing on the https://github.com/eclipse/sumo...
Read more >7 Github Actions Tricks I Wish I Knew Before I Started
I mean, if we set the PR as a draft, there's no need to run all the heavy tests on it, right? Maybe...
Read more >Deploy stalls out, GitHub Action never completes push to ...
If you click on the Github Action on their page, you can see their log output. It shows a load of detail and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I can’t share this info with you in the public repository, you will need to create a support ticket for requesting this info.
We’re acknowledging this is affecting multiple, distinct users of Actions. Creating a support issue is the best way to get the right attention on this. Closing the issue as it is likely not an issue directly caused by the runner itself.