Question 1
A GitHub Actions workflow is failing with an error indicating that a self-hosted runner with the label windows-gpu-large is not available. The administrator confirms that several runners with this label are online and idle. The workflow is running in a private repository. What is the most likely configuration issue preventing the workflow from using the available runners?
graph TD
subgraph GitHub Enterprise Cloud
Org[Organization]
Repo[Private Repo]
Workflow[Workflow Job runs-on: windows-gpu-large]
end
subgraph On-Premises Network
RunnerGroup[Runner Group: 'GPU-Runners']
Runner1[Runner 1 (windows-gpu-large)]
Runner2[Runner 2 (windows-gpu-large)]
end
Workflow -- Needs --> Runner1
Org -- Contains --> Repo
RunnerGroup -- Contains --> Runner1
RunnerGroup -- Contains --> Runner2
Repo -- ??? --> RunnerGroup
Answer and explanation
Correct answer: B
Self-hosted runners are managed in groups, and these groups must be explicitly configured to be accessible by specific repositories or all repositories in an organization. Even if the runners are online and have the correct label, if the runner group is not authorized for the repository where the workflow is running, the job will not be assigned to them.
