I just checked the Travis CI status page, and it's showing a rather large backlog (~120-140 jobs) earlier today. Their site says:
Our database provider has asked to make some changes to the existing primary logs DB that require we stop processing new jobs temporarily. They also mentioned that the S3 issue was causing them trouble, too, and they ALSO had a short API outage. I'm maybe it was just really bad luck that caused a bit of a backlog? AFAIK OSS projects are supposed to get up to 5 builds running concurrently. Maybe it would be worthwhile to attempt to parallel-ize the tests that don't depend on each other in any way? Also, this has nothing to do with this post, but when I saw this email, GMail showed the senders as "Barry .. Tres, Donald", and I thought it said "Trump, Donald". On Fri, Mar 3, 2017 at 4:54 PM, Donald Stufft <don...@stufft.io> wrote: > > On Mar 3, 2017, at 5:53 PM, Tres Seaver <tsea...@palladion.com> wrote: > > Travis also throttles organizations with lots of builds. > > > > I’m seeing if I can get our default limit increased FWIW. > > — > Donald Stufft > > > > > _______________________________________________ > core-workflow mailing list > core-workflow@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 > -- Ryan (ライアン) Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else http://refi64.com/
_______________________________________________ core-workflow mailing list core-workflow@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
