Force build on wrong builder

Ryan Schmidt ryandesign at
Thu Oct 12 13:11:45 UTC 2017

On Oct 12, 2017, at 08:08, Zero King wrote:

> On Thu, Oct 12, 2017 at 07:37:06AM -0500, Ryan Schmidt wrote:
>> You can imagine that this gets worse the more ports you schedule at once, and the more interdependencies they have. And we have lots of python and perl modules, and they tend to have lots of interdependencies. So your forced build of all python modules on the High Sierra builder scheduled 2400 builds, which have so far taken 68 hours, during which no builds from commits could take place. We can let it run, because it's almost done now, and we do need to attempt those builds sooner or later, but I suspect many of those builds could have been avoided if they had been scheduled in smaller batches.
> I saw that a lot of builds were scheduled on the Sierra builder and thought you
> were trying to start another batch but chose the wrong builder.
> I apologize for any inconvenience I've caused.

No worries, like I said we did need to build those ports anyway, and we're still recommending people wait before upgrading to High Sierra to give us time to complete more builds, so the inconvenience is probably low.

I just wanted to be thorough in my response, since I know we haven't documented much about how the buildbot works or the reasons why some things are the way they are.

More information about the macports-dev mailing list