Skip to main content

MAX_IN_PROGRESS_RUNS_PER_REPOSITORY_PER_POLL

Constant MAX_IN_PROGRESS_RUNS_PER_REPOSITORY_PER_POLL 

Source
pub const MAX_IN_PROGRESS_RUNS_PER_REPOSITORY_PER_POLL: usize = 4;
Expand description

The most status=in_progress runs one repository’s job listing may resolve per poll.

Smaller than MAX_QUEUED_RUNS_PER_REPOSITORY_PER_POLL on purpose: this pass exists to catch a needs:-gated job whose run has already started, and on the overwhelmingly common shape it finds nothing and costs one request per run to discover that. Giving the safety net the same budget as the primary signal would double the worst case to buy a rarer case.