3 ms·
does bors limit the commit frequency / PR merge frequency to one merge every test runtime (5 minutes in OP), or does it do something more complex and speculate
by rrss 4y ago
does bors limit the commit frequency / PR merge frequency to one merge every test runtime (5 minutes in OP), or does it do something more complex and speculate / run some stuff in parallel?
OP’s numbers are 120 commits per hour and 5 minute test run, I’m wondering if adopting bors would necessarily reduce that to 12 commits per hour.
- henryfjordan 4y agoBors batches PRs, tests the batch, then merges the whole batch at once. It's made to handle high-throughput repos.
- krab 4y agoIt tries to build all queued changes together at first. So if you don't have any conflicts, there is no throughput limit.
- TheCoelacanth 4y agoWhat about if something in the middle causes a failure? Does it have a git-bisect-like workflow to figure out the bad change?
- krab 4y agoAccording to the README, it bisects. It doesn't matter much for me, though - the batches in our case were never big. https://github.com/bors-ng/bors-ng/blob/master/README.md#how-it-works https://github.com/bors-ng/bors-ng/blob/master/README.md#how...