actions
orphan jobs on the runner
I'm encountering an issue with my runners. They are showing an 'ACTIVE' status, but are not processing any jobs. Furthermore, I'm unable to delete these runners due to a message indicating 'jobs are running,' even though no jobs are actually in progress. I'm looking for assistance to resolve this stuck state.
https://github.com/bytebase/bytebase/settings/actions/runners
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- Go to '...'
- Run '....'
- See error
Expected behavior A clear and concise description of what you expected to happen.
Runner Version and Platform
Version of your runner?
OS of the machine running the runner? OSX/Windows/Linux/...
What's not working?
Please include error messages and screenshots.
Job Log Output
If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.
Runner and Worker's Diagnostic Logs
If applicable, add relevant diagnostic log information. Logs are located in the runner's _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.
probably related to https://www.githubstatus.com/incidents/m7vl0x8k3j9c
Hi @TingluoHuang, there are no incidents for today, but we do occasionally encounter this issue. Do you have any unannounced incidents for today?
$ ps axo stat,ppid,pid,comm | grep -w defunct
Z 1866 3209 esbuild <defunct>
After terminating the zombie processes, the runner script was able to exit properly.
