Documentation

testing._test_pool

(internal) A pool admitting `max_concurrency` leaves at once, each with a `timeout_ms` deadline. A zero or negative `max_concurrency` means "no explicit budget": fall back to a bound that keeps a pathological fan-out from creating thousands of live VM threads while staying above any real machine's core count (the CLI always passes an explicit budget).

Reference version

Signature

function testing._test_pool(max_concurrency: int, timeout_ms: int) -> testing._TestPool throws never

(internal) A pool admitting max_concurrency leaves at once, each with a timeout_ms deadline. A zero or negative max_concurrency means "no explicit budget": fall back to a bound that keeps a pathological fan-out from creating thousands of live VM threads while staying above any real machine's core count (the CLI always passes an explicit budget).

Source:<builtin>/testing/registry.bamlbytes 18518–18864