<div dir="ltr">Donald is our contact with Travis, so I've explicitly added him to this email.<div><br></div><div>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; see <a href="https://travis-ci.com/plans">https://travis-ci.com/plans</a> to get an idea of what we're getting for free). CPython itself uses 3 of those with any single PR or merge into a branch (docs, Py_DEBUG, coverage).<br><br>Now normally this works out great for us since CPython is probably one of the more active projects that gets to use this increased budget, and so we typically take a chunk of the 25 concurrent builds happily and get our builds started very promptly. But at the sprints we ran up against cryptography and their crazy build needs: <a href="https://travis-ci.org/pyca/cryptography">https://travis-ci.org/pyca/cryptography</a> . IOW having every major Python project using Travis' free service at once hit us hard.</div><div><br></div><div>As to whether we can get more of a budget for the sprints at PyCon US (or any other conference), I don't know. Maybe Donald could tell us more detail and/or find out if next year we can plan ahead to get a temp boost for the four days. Otherwise we're talking about making PyCA suffer year-round by having them have to get their own quota or something.<br><br><br><div class="gmail_quote"><div dir="ltr">On Wed, 24 May 2017 at 14:46 Guido van Rossum <<a href="mailto:guido@python.org">guido@python.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.<br></div><div class="gmail_extra"></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 24, 2017 at 2:38 PM, Eric Snow <span dir="ltr"><<a href="mailto:ericsnowcurrently@gmail.com" target="_blank">ericsnowcurrently@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">tl;dr Could we temporarily bump our cap on concurrent travis builds<br>
during sprints?<br>
<br>
During the sprints at PyCon we've been running into a serious<br>
bottleneck with travis. Having an extra allowance for builds already<br>
is great, but during sprints even that gets swamped. I am not sure<br>
what projects contribute most to the problem, but I'm pretty sure it<br>
isn't CPython (essentially 2 builds per PR). Regardless, with the new<br>
workflow this bottleneck significantly impacts the higher pace that<br>
usually takes place at sprints. Would it make sense to see if the<br>
Travis folks would be willing to bump our limit temporarily during<br>
each sprint?<br>
<br>
-eric<br>
_______________________________________________<br>
core-workflow mailing list<br>
<a href="mailto:core-workflow@python.org" target="_blank">core-workflow@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/core-workflow" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/core-workflow</a><br>
This list is governed by the PSF Code of Conduct: <a href="https://www.python.org/psf/codeofconduct" rel="noreferrer" target="_blank">https://www.python.org/psf/codeofconduct</a><br>
</blockquote></div><br><br clear="all"><br></div><div class="gmail_extra">-- <br><div class="m_6014501131780547038gmail_signature" data-smartmail="gmail_signature">--Guido van Rossum (<a href="http://python.org/~guido" target="_blank">python.org/~guido</a>)</div>
</div>
_______________________________________________<br>
core-workflow mailing list<br>
<a href="mailto:core-workflow@python.org" target="_blank">core-workflow@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/core-workflow" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/core-workflow</a><br>
This list is governed by the PSF Code of Conduct: <a href="https://www.python.org/psf/codeofconduct" rel="noreferrer" target="_blank">https://www.python.org/psf/codeofconduct</a><br>
</blockquote></div></div></div>