Workflow can block if insufficient runners available
ximon18 opened this issue · comments
This can happen if all available runners start running jobs that themselves wait for cross-compiled artifacts to be produced by other jobs which are not yet assigned to a runner.
This is a consequence of the work-around used to make some matrix job invocations wait without making the entire matrix job wait, as GitHub Actions doesn't itself support that.
This isn't typically a problem if using GitHubs own hosted runners, but when using a limited pool of applicable runners (e.g. with self-hosted runners) it can be a problem.
Worked around in https://github.com/NLnetLabs/ploutos/releases/tag/v7.1.0 by allowing the operator to specify a separate pool of runners for cross-compilation via the new cross_runs_on workflow input.