Flow: say why a job waits when every runner that could take it is full or short of room issue #259 closed: completed andymccall opened this · 0 comments
andymccall set labels bug ·
closed by change 58cbf42447bc ·
andymccall set labels bug ·
closed by change 58cbf42447bc ·
Seen 2026-10-18: oxygenhub-gcp runs 30 and 31 waited an hour with an empty waiting reason while earth-1 showed 2 of 3 slots free (its memory room held by the hub's Rust tests) and mars-1/plex-1 ran long doomsdayone jobs. The placement pass only explains jobs no runner can take at all; a job that fits a runner only when it has more room, or one whose turn hasn't come behind higher-priority work, says nothing. It should say which: 'runners that can take it are busy (earth-1: memory 2 GiB needed, 1.4 GiB free; mars-1, plex-1: running)' or 'behind N higher-priority jobs'. Insights (issue #257) charts the pickup time; this explains a single job.