self hosted runner is not accepting jobs from queue.
Problem
Describe the bug Self hosted idle runner is not consuming queued jobs (runner version 263, release version). To Reproduce Steps to reproduce the behavior: 1. Assume you have a runner in the state offline (self-hosted) 2. New action workflow is triggered 3. Create a new runner (config and run). We scale them automatically 4. New runner is not consuming the queued jobs. This was working perfectly for a few months, but got recently broeken. 5. It got a bit more strange, trigger a new workflow. The runner wil see this jobs, start an upgrade to the prereleas, see #581 . And jobs stars, Queued jobs remains stucks today (2020-07-15 between 12 and 18 CET). Now around 20:30 CET the queued jobs are consumed as well. But all still strange since it is the event of the second trigger that cause the update of a non released version. Should 267 not be released? Expected behavior Runner in the idle status should consume jobs (labels are matching). Runner Version and Platform GitHub cloud + runner version 263 OS of the machine running the runner? OSX/Windows/Linux/... What's not working? No error message, see behaviror above. 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 n/a reference: our setup is available here: https://github.com/philips-labs/terraform-aws-github-runner
Error Output
error message, see behaviror above.
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: self hosted runner is not accepting jobs from queue.
Having this issue right now. I have idle workers "listening for jobs" and nothing happens. Workflows are not started. I tried cancelling and restarting but it doesn't seem to help. I started to see this today. Anyone else experiencing this at the moment?
Trust Score
5 verifications
- 1
Having this issue right now. I have idle workers "listening for jobs" and nothin
Having this issue right now. I have idle workers "listening for jobs" and nothing happens. Workflows are not started. I tried cancelling and restarting but it doesn't seem to help. I started to see this today. Anyone else experiencing this at the moment?
Validation
Resolved in actions/runner GitHub issue #592. Community reactions: 8 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep