Documentation Index
Fetch the complete documentation index at: https://docs.trunk.io/llms.txt
Use this file to discover all available pages before exploring further.
Set higher test concurrency for failure isolation without slowing down your main merge queue
When a batch of PRs fails and needs to be split apart to identify the culprit, you want those
bisection tests to run as fast as possible so developers get quick feedback about what broke.
Previously, bisection tests shared the same concurrency limit as your main queue, meaning the
isolation process could slow down other PRs waiting to merge. With independent concurrency settings,
you can configure bisection to run at higher concurrency (spinning up more test runners to isolate
failures ASAP) while keeping your main queue at its optimal setting.
This means faster root cause identification when batches fail, no impact on your main queue’s
throughput during failure investigation, and the flexibility to optimize each workflow
independently. You can be aggressive about isolating problems without sacrificing the steady flow of
successful PRs through your queue.
Read the Docs
to learn more
