It looks like the situation stabilised. The current Travis CI status is "Identified - We have continued to investigate this issue. We have a fix that we are sending to affected customers to have a wider validation before deploying it to all customers. Thanks again for your patience."
It seems that they implemented a fix for our builds - I have not seen a build failed because of pip-install in the last 24 hours. So hopefully we will finally have stable tests on Travis. J. On Thu, May 9, 2019 at 7:48 AM Jarek Potiuk <[email protected]> wrote: > Other people are still experiencing it as well: Travis engineers re-opened > the issue: https://www.traviscistatus.com/ I will keep you posted. > > J. > > On Wed, May 8, 2019 at 3:21 PM Jarek Potiuk <[email protected]> > wrote: > >> It's still not fully fixed . >> https://travis-ci.org/apache/airflow/jobs/529764185 >> >> On Wed, May 8, 2019 at 11:39 AM Jarek Potiuk <[email protected]> >> wrote: >> >>> Seems that the issue is resolved by Travis 11 hours ago but I saw at >>> least one case where the build stalled again. I will monitor the situation >>> and see if it has been resolved indeed. >>> >>> J. >>> >>> On Tue, May 7, 2019 at 6:12 AM Jarek Potiuk <[email protected]> >>> wrote: >>> >>>> I think we have to be a little patient :(. >>>> >>>> They are still working on it - and the workarounds they provided are >>>> not really applicable to our case. And fix they applied (fixing failing NAT >>>> instances) does not seem to work. >>>> More information here: >>>> https://www.traviscistatus.com/incidents/kyf149kl6bvp?u=3g7kt113nmgs >>>> >>>> J. >>>> >>>> On Mon, May 6, 2019 at 4:59 PM Jarek Potiuk <[email protected]> >>>> wrote: >>>> >>>>> Hello Everyone, >>>>> >>>>> Finally Travis acknowledged that people have problem of slow or >>>>> stalled builds from within docker container and they are apparently >>>>> investigating it. You can subscribe for the incident status reports here: >>>>> >>>>> https://www.traviscistatus.com/incidents/kyf149kl6bvp?u=3g7kt113nmgs >>>>> >>>>> >>>>> J. >>>>> >>>>> -- >>>>> >>>>> Jarek Potiuk >>>>> Polidea <https://www.polidea.com/> | Principal Software Engineer >>>>> >>>>> M: +48 660 796 129 <+48660796129> >>>>> E: [email protected] >>>>> >>>> >>>> >>>> -- >>>> >>>> Jarek Potiuk >>>> Polidea <https://www.polidea.com/> | Principal Software Engineer >>>> >>>> M: +48 660 796 129 <+48660796129> >>>> E: [email protected] >>>> >>> >>> >>> -- >>> >>> Jarek Potiuk >>> Polidea <https://www.polidea.com/> | Principal Software Engineer >>> >>> M: +48 660 796 129 <+48660796129> >>> E: [email protected] >>> >> >> >> -- >> >> Jarek Potiuk >> Polidea <https://www.polidea.com/> | Principal Software Engineer >> >> M: +48 660 796 129 <+48660796129> >> E: [email protected] >> > > > -- > > Jarek Potiuk > Polidea <https://www.polidea.com/> | Principal Software Engineer > > M: +48 660 796 129 <+48660796129> > E: [email protected] > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> E: [email protected]
