GitHub Community
Troubleshooting skipped job #25648
-
|
Hi, For some reason I have a job that runs for 20-30min, then terminates as skipped and I can see “skipped 5 minutes ago in 24m 34s”. I can see logs from this job (unless I refresh the page), so it is not “if” statement issue. However when I refresh the page logs dissapear and I can see yellow spinner near the step on which it was terminated (which means step is in progress). Is there any way to troubleshoot this issue ? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
I’m pretty shure the problem with your job is that the GitHub - actions/runner: The Runner for GitHub Actions Runner.Worker process died or lost the connection to github. I’m able to force this ui behavior The worker uploads the log of the current running step after it finished, in your case it never finished correctly and only live logs were visible. Github discards live logs after streaming then to the UI, so they are gone if you reload the page. I wonder why such a job is marked as skipped in this situation, it clearly failed.
If you used a self-hosted runner upload / look into the files in the _diag folder of the runner root folder. These files might contain more information about your issue. |
Beta Was this translation helpful? Give feedback.
I’m pretty shure the problem with your job is that the GitHub - actions/runner: The Runner for GitHub Actions Runner.Worker process died or lost the connection to github.
It might be possible that your job caused the github hosted runner to run out of diskspace, then the runner died.
I’m able to force this ui behavior
The worker uploads the log of the current running step after it finished, in your case it never finished correctly and only live logs were visible. Github discards live logs after streaming then to the UI, so they are gone if you reload the page.
I wonder why such a job is marked as skipped in this situation, it clearly failed.