actions
Github Action workflows Hang
Seems like there is an issue with Github Action Runners. all our different actions looks 'wierd'. The job output seems collapsed into a single Text output and seems ilke the job are never ends.
just created a simple dummy action to test it and it got reproduce.
name: Tester
on:
push:
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
with:
fetch-depth: 0
- name: echo
run: |
echo Bla
Output is endless while at the end seems like job cannot complete the cleanup process.
Post job cleanup.
/usr/bin/git version
git version 2.47.0
Temporarily overriding HOME='/home/runner/work/_temp/ab3e00c9-67e9-4e9a-83c1-740a432d20c6' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
http.https://github.com/.extraheader
/usr/bin/git config --local --unset-all http.https://github.com/.extraheader
/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
Cleaning up orphan processes
Anyone else encountering such issues? havent seen anything yet on Github-Status indicating the issue
same issue here, tried renaming the workflow, canceling the workflow doesn't work either, seems github never recognizes the output properly and considers the job "queued" forever even though the text in logs shows it as complete and successful
Facing same issue even though the runners are hosted private. Either it is queues to pick runner or getting stuck at Cleaning up orphan processes.
same issue here, also showing last successful build is still running.
same issue here, tried renaming the workflow, canceling the workflow doesn't work either, seems github never recognizes the output properly and considers the job "queued" forever even though the text in logs shows it as complete and successful
renaming the job doesn't work either, left image is how it looks, right image is how it should look:
here is my setup, still broken, haven't tried different OS from ubuntu-latest:
on:
push:
branches:
- "*"
jobs:
deploy_job:
runs-on: ubuntu-latest
name: build-deploy
steps:
...
Tested it both from Organization account and private account, same result. also, seems like both jobs that worked yesterday and the ones that are failing today are using the SAME Ubuntu image version and OS.
Image: ubuntu-22.04
Version: 20241015.1.0
Image Provisioner 2.0.384.1
so it doesnt seems to be related to any update on the runner version Jobs are able to execute the flow, its just that they are failing to cleanup the process.
also, cancle does not work.
My Deploymemt Is working fine and its done i can verify it on my server but still action showing queued.
same here, stuck on Cleaning up orphan processes - even for self-hosted runners.
tried different runs-on:
- ubuntu-latest stuck
- ubuntu-22.04 stuck
- ubuntu-20.04 stuck
i'm out of options, seems the issue is platform independent, workflow independent, job name independent, branch and repository independent
Same issue. Self Hosted K8S Runner.
I see that the pods start and work, but the feedback in the actions (web ui) is missing. It looks like all runners are stuck
canceling the workflow actually does cancel it in logs if its still in progress however it doesn't affect the UI still showing as "queued"; canceling after Post job cleanup. has no effect on logs.
also same to us
https://github.com/Prompt-oven/prompt-oven/actions/runs/11588704913/job/32262874626?pr=20
for anyone waiting:
- it seems to be a UI issue, not a problem of actually getting the workflow to finish internally, simply ignore the UI "queued" state for now and read the logs
- if you know how yours logs should end and your logs end without errors you can consider the run a success and proceed with your day
An incident has been filed: https://www.githubstatus.com/incidents/9yk1fbk0qjjc
