[core-workflow] travis bottleneck at sprints

[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 <ericsnowcurrently at gmail.com>
wrote:

> 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 contribute most to the problem, but I'm pretty sure it
> isn't CPython (essentially 2 builds per PR).  Regardless, with the new
> workflow this bottleneck significantly impacts the higher pace that
> usually takes place at sprints.  Would it make sense to see if the
> Travis folks would be willing to bump our limit temporarily during
> each sprint?
>
> -eric
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>



-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20170524/5538720d/attachment.html>