This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author db3l
Recipients db3l, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2017-04-28.01:42:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1493343771.43.0.63106692306.issue30173@psf.upfronthosting.co.za>
In-reply-to
Content
Yeah, there were a few transient build errors while I was getting the buildbot back online.  My initial attempt to fix this ticket involved using the VS 2015 installer which turned out very badly, so I had to fall back to an older VM image and start over.  But the older image had an older buildbot version which didn't work with the git workflow, which hit a few pending builds before I got it fixed.

I'm not yet sure if there may be some other fallback (e.g., the link error in the recent 3.x build seems familiar but I can't recall why offhand)
History
Date User Action Args
2017-04-28 01:42:51db3lsetrecipients: + db3l, paul.moore, vstinner, tim.golden, zach.ware, steve.dower
2017-04-28 01:42:51db3lsetmessageid: <1493343771.43.0.63106692306.issue30173@psf.upfronthosting.co.za>
2017-04-28 01:42:51db3llinkissue30173 messages
2017-04-28 01:42:50db3lcreate