Travis CI timeouts for MacPorts builds

Ryan Schmidt ryandesign at macports.org
Mon Sep 7 14:38:02 UTC 2020



> On Sep 7, 2020, at 08:50, Mojca Miklavec wrote:
> 
> On Mon, 7 Sep 2020 at 10:46, Ralph Seichter wrote:
>> 
>> I fail to remember the last time one of my builds successfully passed
>> Travis CI. All I see are timeouts [1]. Other peoples' jobs apparently
>> make it through Travis OK, so I wander what I can do to increase my
>> chances?
> 
> By far the best thing would be to implement the functionality that
> would allow firing up a clean VM, do the build, close the VM & destroy
> it, and run this on our own buildbot workers.
> 
> This requires both manpower to implement the functionality as well as
> additional hardware resources to run the builds.
> If we solve the first part, I guess we should be able to solve the
> second one as well.
> If you volunteer to do some research / work in this area ... that
> would likely be the most significant step in "increasing your chances"
> ... probably up to 100% for the ports that have no chance in building
> in < 50 minutes on a super slow hardware owned by Travis :)

I feel that the Azure Pipelines are already giving us good results on current systems, and we could probably turn off the Travis builds for the systems that Azure also covers.



More information about the macports-dev mailing list