The runner always in busy state even the job is finished.

Describe the bug I have self-hosted deployment in kubernetes. I had a deployment job ran failed, but the runner can’t pickup new job, checked the runner logs see it’s stuck at 2020-09-11 03:47:04Z: Running job: Deploy even I can see the job failed on Actions tab.

To Reproduce Steps to reproduce the behavior:

1. don’t know how to reproduce it

Expected behavior the runner properly complete the job no matter success or failure, so the subsequent job won’t be impacted.

Runner Version and Platform

Version of your runner? 2.273.1

OS of the machine running the runner? OSX/Windows/Linux/… 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.

2020-09-11 02:27:55Z: Running job: Build 2020-09-11 02:35:52Z: Job Build completed with result: Succeeded 2020-09-11 02:35:55Z: Running job: Build 2020-09-11 02:36:27Z: Job Build completed with result: Failed 2020-09-11 02:36:30Z: Running job: Build 2020-09-11 02:37:25Z: Job Build completed with result: Succeeded 2020-09-11 02:37:28Z: Running job: Build 2020-09-11 02:38:14Z: Job Build completed with result: Succeeded 2020-09-11 02:38:17Z: Running job: Deploy 2020-09-11 02:38:32Z: Job Deploy completed with result: Failed 2020-09-11 03:11:24Z: Running job: Build 2020-09-11 03:12:02Z: Job Build completed with result: Succeeded 2020-09-11 03:12:11Z: Running job: Deploy 2020-09-11 03:12:26Z: Job Deploy completed with result: Failed 2020-09-11 03:14:41Z: Running job: Create Release 2020-09-11 03:15:58Z: Job Create Release completed with result: Failed 2020-09-11 03:18:13Z: Running job: Build 2020-09-11 03:18:48Z: Job Build completed with result: Succeeded 2020-09-11 03:18:58Z: Running job: Deploy 2020-09-11 03:19:12Z: Job Deploy completed with result: Failed 2020-09-11 03:20:49Z: Running job: Create Release 2020-09-11 03:23:26Z: Job Create Release completed with result: Failed 2020-09-11 03:46:17Z: Running job: Build 2020-09-11 03:46:54Z: Job Build completed with result: Succeeded 2020-09-11 03:47:04Z: Running job: Deploy

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.

[BrightRan]

A GitHub Community ticket that reports the similar issues: https://github.community/t/github-actions-workflow-stuck/132330

All the jobs run on the self-hosted runners in the workflow were completed successfully, but the workflow run keeps displaying as in progress with the yellow icon. And other queued jobs can’t use the self-hosted runners because they are in busy. Reconnect the self-hosted runners and restart the hosted machines does not work.

[rubencodes]

I’m definitely still seeing this happen on my self-hosted runner version 2.293.0.

I also tried the “Cancel workflow” button which indicated it would cancel the run, but it did not.

This is particularly troubling because I can’t seem to access my artifacts until after the job completes. It eventually completed but roughly ~9m after it should have completed.