[Python-Dev] Appveyor builds fail on Windows for 3.6 backports.
steve.dower at python.org
Fri Jun 23 16:14:03 EDT 2017
We could improve life for everyone even more if we built Tcl/Tk once per update and made it a binary dependency. Nobody is updating our version of it regularly anyway, and this would significantly improve build time in CI.
The externals script probably just needs some retry logic. Doesn’t look like a “throw it all out” problem to me.
Top-posted from my Windows phone
From: Terry Reedy
Sent: Friday, June 23, 2017 11:44
To: python-dev at python.org
Subject: Re: [Python-Dev] Appveyor builds fail on Windows for 3.6 backports.
On 6/23/2017 2:24 PM, Zachary Ware wrote:
> On Fri, Jun 23, 2017 at 11:36 AM, Terry Reedy <tjreedy at udel.edu> wrote:
>> Example: appveyor passes for
>> Appveyor build fails for 3.6 backport
>> The compile and build errors have nothing to do with the patch.
>> This failure is routine; turning off appveyor for 3.6, until fixed, would
>> reduce noise.
>> I presume this is a workflow issue, but I don't know if Windows experts
>> would see it.
> I had not seen that failure before, but it is troubling. For
> AppVeyor, it looks like we might be able to get around it by using the
> `cache` feature (which we should probably do anyway), but if that
> failure happens routinely otherwise, we may have to completely rethink
> the approach I've taken in https://bugs.python.org/issue30450
If by 'cache', you mean keep a current build of the main x.y branch, and
only recompile what is needed, and skip compile for .py and .rst only
patches, thereby speeding up CI testing, I would be all in favor.
Terry Jan Reedy
Python-Dev mailing list
Python-Dev at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev