Repository: actions/runner

Issue #2768: Self-hosted runner group picks up wrong job, and doesn't pick up the right job
Created: 2023-08-15T11:18:59Z
Describe the bug
I have 5 GitHub runners running side by side on a Mac Mini. They are separated into two runner groups,

Default
client-deploy.

The client-deploy group was limited to playground repository. So far I have observed two unexpected behaviours.


occasionally runner in client-deploy group picked up job from repository other than playground
Given sample workflow from another repository not in the allowed list of the runner group, sometimes the runner picked up the job regardlessly. It happens frequently enough, but when I trigger the workflow again, usually the right agents picked up the job
Workflow file

Job info



runner in client-deploy group didn't pick up job from playground repository

Here you see clientdeploy instead of client-deploy as the runner group name, it was a desperate attempt to see if - made a difference.

This happens 100%. But curiously, if I add a label to the runner and specify runner with label instead of runner group name, the runner was able to pick up the job.
Workflow file

Job info




To Reproduce
I don't think it would be easy to replicate my setup (Mac OS, multiple runners on same machine). However if you have a troubleshoot script, I am happy to run it and report back. I tried this guide, didn't find anything.
Expected behavior
Runner in client-deploy group picks up job from approved repository, not jobs from other repositories
Runner Version and Platform
Version of your runner?
2.307.1
OS of the machine running the runner? OSX/Windows/Linux/...
Model Name: Mac mini
Model Identifier: Mac14,3
Model Number: Z16L00005ZP/A
Chip: Apple M2
System Version: macOS 13.2.1 (22D68)

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.

Duplicate issue #2825: Wrong runner runs on job
Created: 2023-09-04T17:29:30Z
I have set up a server for staging purposes.
my staging workflow yaml file:
name: monbatiment STAGING
on:
    push:
        branches: [ staging ]
    pull_request:
        branches: [ staging ]
jobs:
    build:
        runs-on: self-hosted
        strategy:
            matrix:
              runner: [ STAGING-front ]
        steps:
        - uses: actions/checkout@v2

in github actions:
build (STAGING-front)
but this is the output for "Setup Job":
Current runner version: '[2](https://github.com/MonBatiment/**REPO**/actions/runs/6076267689/job/16483963088#step:1:2).[3](https://github.com/MonBatiment/**REPO**/actions/runs/6076267689/job/16483963088#step:1:3)08.0'
Runner name: **'novadia-front'**
Runner group name: 'Default'
Machine name: 'novadia'
GITHUB_TOKEN Permissions
Secret source: Actions
Prepare workflow directory
Prepare all required actions
Getting action download info
Download action repository 'actions/checkout@v2' (SHA:ee0669bd1cc5[4](https://github.com/MonBatiment/**REPO**/actions/runs/6076267689/job/16483963088#step:1:4)29[5](https://github.com/MonBatiment/**REPO**/actions/runs/6076267689/job/16483963088#step:1:5)c223e0bb666b733df41de1c5)
Complete job name: build (STAGING-front)

the runner novadia-front runs. but not the intended STAGING-front ???
earlier it was mkhome-front that was running. another separate runner i have for another workflow

Closing comment (2023-10-03T10:23:03Z): Closing as a duplicate of #2768