pub const MAX_QUEUED_RUNS_PER_REPOSITORY_PER_POLL: usize = 6;Expand description
The most status=queued runs one repository’s job listing may resolve per
poll.
The primary signal gets the larger cap. Past it the reported count is a
floor rather than a total, which is safe in the direction that matters:
e1 clamps demand to max_capacity and the host ceiling anyway, so a
repository with more than this many queued runs is one whose real demand
exceeds any realistic host’s capacity — the allocation is already pinned at
the ceiling and a larger number would not change it. Successive polls resolve
the rest as the earlier runs drain.