Re: [core-workflow] travis bottleneck at sprints

2017-05-25 Thread Donald Stufft
> On May 25, 2017, at 4:49 PM, Brett Cannon wrote: > > Donald is our contact with Travis, so I've explicitly added him to this email. > > To give some details: we get 25 concurrent jobs across all the various > "official" Python projects on GitHub hosted under the Python, PyPA, and PyCA > org

Re: [core-workflow] travis bottleneck at sprints

2017-05-25 Thread Brett Cannon
Donald is our contact with Travis, so I've explicitly added him to this email. To give some details: we get 25 concurrent jobs across all the various "official" Python projects on GitHub hosted under the Python, PyPA, and PyCA organizations (which is a substantial bump from what most projects get;

Re: [core-workflow] travis bottleneck at sprints

2017-05-24 Thread Guido van Rossum
I've noticed that too; the python/mypy project is also experiencing slow builds (as is mypy/typeshed). I don't know how to contact Travis for this though. On Wed, May 24, 2017 at 2:38 PM, Eric Snow wrote: > tl;dr Could we temporarily bump our cap on concurrent travis builds > during sprints? >

[core-workflow] travis bottleneck at sprints

2017-05-24 Thread Eric Snow
tl;dr Could we temporarily bump our cap on concurrent travis builds during sprints? During the sprints at PyCon we've been running into a serious bottleneck with travis. Having an extra allowance for builds already is great, but during sprints even that gets swamped. I am not sure what projects