I’m just starting to try-out Bors for our open source project. I’ve read that
bors r+ is doing batch jobs in the
staging branch, using a queue. But when commenting
bors try on several pull requests, it seems that the
trying branch gets overwritten by the new test, even when Travis didn’t finish the last one.
This results in some interesting build fails, as Travis was still booting and the commit for which it was booting disappeared. An example from the Travis logs:
$ git checkout -qf 093d7037046359b1d8fe8c7d0ef27f60acc11884 fatal: reference is not a tree: 093d7037046359b1d8fe8c7d0ef27f60acc11884 The command "git checkout -qf 093d7037046359b1d8fe8c7d0ef27f60acc11884" failed and exited with 128 during
One last note: I’ve configured bors-ng in the dashboard to use a branch called “testing” for the try command. Don’t know if this matters.