Author db3l
Recipients db3l, jeremy.kloth, jkloth, miss-islington, pablogsal, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-12-11.03:29:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544498990.72.0.788709270274.issue35433@psf.upfronthosting.co.za>
In-reply-to
Content
Ah, got it (and see the pipelines comment by Steve).

Jeremy, I suspect you might actually be able to restart the most recent 3.6 builds on my builders since you were the committer.  It changed in Sep to only allow python-core users and the "owner" of the build.  Though I don't think I learned for sure if owner was the author of the commit or just the actual committer.

I think Zachary was going to look into it time permitting.  We probably need a different GitHub group for buildbot owners or something.

Separately, I think in the context of this issue I think it's fair to say that the commit need not be rolled back.  I have to imagine that anyone trying to build 3.6 using VS 2015 at this point is going to be better represented by Jeremy's worker than mine (in terms of VS point release and default SDK installation), and I expect to be able to resolve any remaining issues worker-side once some 3.6 builds go through.
History
Date User Action Args
2018-12-11 03:29:50db3lsetrecipients: + db3l, paul.moore, vstinner, tim.golden, jkloth, jeremy.kloth, zach.ware, steve.dower, pablogsal, miss-islington
2018-12-11 03:29:50db3lsetmessageid: <1544498990.72.0.788709270274.issue35433@psf.upfronthosting.co.za>
2018-12-11 03:29:50db3llinkissue35433 messages
2018-12-11 03:29:49db3lcreate