You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If GitHub finds an online and idle runner at a certain level that matches the job's runs-on labels, the job is then assigned and sent to the runner.
If GitHub doesn't find an online and idle runner at any level, the job is queued to all levels and waits for a matching runner from any level to come online and pick up the job.
If the job remains queued for more than 24 hours, the job will fail.
This is a deprecated feature for GitHub Cloud as "registration-only" runners are no longer needed due to GitHub changing their runner routing logic to no longer fail a workflow run if it targets a runner label that there are no registered runners for.
The await code here has nothing to be with the ability of GH of continue if no runner is present.
The await code is done to check if if the runner can register successfully and be able to log the reason why is not properly registering or being launched and in last instance destroy all the cloud resources in case the runner has not even launched
Circa September 2021, GitHub modified the runner routing logic so jobs don't fail anymore when there is no runner available with the required labels.
This eliminates the need for a substantial amount of workarounds in out code, and we should probably consider removing them.
Documentation
github/docs#9307
actions/actions-runner-controller#909
Code
terraform-provider-iterative/iterative/resource_runner.go
Lines 224 to 262 in fa9c7f8
terraform-provider-iterative/iterative/utils/runner.go
Lines 1 to 40 in fa9c7f8
terraform-provider-iterative/iterative/resource_machine.go
Lines 278 to 289 in fa9c7f8
The text was updated successfully, but these errors were encountered: