Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stopped runners are still used to execute jobs #3669

Open
Sh4d1 opened this issue Jan 22, 2025 · 0 comments
Open

Stopped runners are still used to execute jobs #3669

Sh4d1 opened this issue Jan 22, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@Sh4d1
Copy link

Sh4d1 commented Jan 22, 2025

Hey! Not sure this is the right place, feel free to tell me if it needs posting elsewhere.

Describe the bug
When using self hosted runner, it recently began to use already stopped runners to execute workflow. The runner is marked down in the runner page, and the job is stuck with:

Waiting for a runner to pick up this job...
Job is about to start running on the runner: <runner> (organization)

Then, cancelling the job waits until 10 min (the timeout I guess) to really cancel the job. And when I retry it tries again on the same shutdown runner.
Also, I have an error when force removing it from the runner page.
Any ideas?

It's worth noting that the runners get shutdown without too much notice, but imho it should not be an issue.

@Sh4d1 Sh4d1 added the bug Something isn't working label Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant