We didn't really experience this at the Bloomberg sprints this fall, but the sprint size was quite a bit smaller than the PyCon sprints.
On Fri, Dec 21, 2018 at 3:07 PM Sumana Harihareswara <[email protected]> wrote: > Donald and Dustin: have we been running into these kinds of Travis > problems in the past few months or does it seem to have settled down? > > -- > Sumana Harihareswara > Changeset Consulting > https://changeset.nyc > > On 5/19/18 4:35 PM, Brett Cannon wrote: > > On Fri, May 18, 2018, 06:08 Dustin Ingram, <[email protected]> > wrote: > > > >> I did reach out to the one contact we had there from when GCP/Fastly > >> were having issues that affected Travis/PyPI (Emma) on Monday, but got > >> no response. > >> > > > > If Travis doesn't work out then let Steve Dower and me know and we can > see > > if we can get you extra credits on VSTS (teammate of mine was already > > working with Jason at the PyCon sprints to get setuptools up on > > PyPA.visualstudio.com). > > > > -Brett > > > > > >> D. > >> > >> On Fri, May 18, 2018 at 8:54 AM, Sumana Harihareswara <[email protected] > > > >> wrote: > >>> In my opinion, this kind of bottleneck is likely to happen more > >> frequently as we increase PyPA development activity, so it'd be worth > >> asking Travis to bump up our account's oomph. (I am very tired and on a > >> train so please forgive handwavy wording.) Do we have a contact there? > >>> > >>> -- > >>> Sumana Harihareswara > >>> Changeset Consulting > >>> https://changeset.nyc > >>> > >>> On 05/16/2018 04:36 PM, Dustin Ingram wrote: > >>>> Thanks for the report. I reverted the commit that caused this in > >>>> https://github.com/pypa/warehouse/pull/4015, however it might take a > >>>> bit for this to get deployed to PyPI because there's currently a > >>>> pretty long backlog in Travis due to all the PyPA development > >>>> happening during the sprints. > >>>> > >>>> D. >
