Hi Peff, On Thu, 23 Mar 2017, Jeff King wrote: > My pattern is particularly spiky from Travis's perspective, because once > a day I rebase everything on top of master and push them the whole thing > in a bunch. So they 75 branches, all at once. That seems like it would > be ripe for throttling (though I would much rather they just queue the > builds and do them one at a time). Travis is optimized for Continuous Integration, i.e. one or maybe two integration branches that merge PRs every once in a while. What we would need is Continuous Testing, really, because we do not do Continuous Integration at all. On the point of the sekrit variable: all I tried to do is to avoid overwhelming the (currently) single VM with plenty of jobs. If the build & test would not take so darned long on Windows due to going in and out of the POSIX emulation layer a gazillion times (caused by intense shell scripting), the tests could be faster. But that would require a massive amount of work, and I simply have too much on my plate to take that task on in addition. If you have an idea how to prevent the overloading of the VM by any means that does not involve that token, please tell me. Ciao, Dscho