On Mon, Aug 15, 2016 at 4:38 PM, Glyph Lefkowitz <gl...@twistedmatrix.com> wrote:
There's a lot that we can do to make Travis almost that fast, with pre-built Docker images and cached dependencies. We haven't done much in the way of aggressive optimization yet. As recently discussed we're still doing twice as many builds as we need to just because we've misconfigured branch / push builds :). Hm... pre-built dockers also takes effort to keep them updated... and then we will have a KVM VM starting inside a docker in which we run the tests... ...and we would not be able to test the inotify part. Not true: > > > 1. We can have one non-containerized builder (sudo: true) for testing > inotify; no need for KVM-in-Docker (also you can't do that without a > privileged container, so, good thing) > > I'm curious about the details of how such a configuration would work. Since there is only one travis configuration per repository (well, per branch, technically, don't think that makes a difference here) and the sudo configuration is global (isn't it?), I always though either a project had to pick sudo or not sudo and you couldn't have a mix of builds with each. (Wonky quoting thanks to gmail's wonky web interface, sorry) Jean-Paul
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
