On Sat, Aug 26, 2017 at 1:16 PM, Daniel James via Boost < boost@lists.boost.org> wrote:
On 26 August 2017 at 18:02, Peter Dimov via Boost <boost@lists.boost.org> wrote:
Daniel James wrote:
But we don't rely that much on the testers nowadays, so this would be less of an issue.
I do. The turnaround on Travis is pretty terrible at the moment, and that's going to get worse as more modules use it.
While I'm a big fan of Boost's test system, and believe that it is an awesome resource that can't be replicated on the common CI services (lots of platforms and compiler versions/configs!), I also think that good per-commit CI on a service like travis is hugely important. Maybe someone should present a proposal to the steering committee to start paying for boostorg's account to have additional build resources? Tom