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
Describe the bug
When scaling runners based on TotalNumberOfQueuedAndInProgressWorkflowRuns it seems that the maximum number of possible runners are currently 60.
Having testet with a workflow with 170 jobs (created by matrix), we only reached 50 runners.
Describe the bug
When scaling runners based on
TotalNumberOfQueuedAndInProgressWorkflowRuns
it seems that the maximum number of possible runners are currently 60.Having testet with a workflow with 170 jobs (created by matrix), we only reached 50 runners.
We think the issue is related to missing pagination handling of the ListWorkflowJobs api here: https://github.com/actions-runner-controller/actions-runner-controller/blob/48923fec562126e2ffe575c9d7694d18c0a56f3d/controllers/autoscaling.go#L70
The default pagination of that API is 30, and that correlates with what we see in the controller manager logs.
Checks
To Reproduce
HorizontalRunnerAutoscaler
that usesTotalNumberOfQueuedAndInProgressWorkflowRuns
, with a limit of more than 60.Expected behavior
Expected the number of runners to be equal to the number of jobs created in the workflow.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: