<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-AU>Correct, and I wasn't planning on it. The default VSTS machines don’t have the right compiler, and I’m not about to start managing VMs for 2.7 at this stage.</span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Top-posted from my Windows 10 phone</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:vstinner@redhat.com">Victor Stinner</a><br><b>Sent: </b>Monday, June 4, 2018 10:07<br><b>To: </b><a href="mailto:steve.dower@python.org">Steve Dower</a><br><b>Cc: </b><a href="mailto:python-committers@python.org">python-committers</a><br><b>Subject: </b>Re: [python-committers] Turning off AppVeyor as required</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>By the way, Python 2.7 doesn't have AppVeyor nor VSTS?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Is there a plan to add VSTS to Python 2.7?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Victor</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2018-06-04 18:46 GMT+02:00 Steve Dower <steve.dower@python.org>:</p><p class=MsoNormal>> On 04Jun2018 0932, Victor Stinner wrote:</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> 2018-06-04 18:18 GMT+02:00 Brett Cannon <brett@python.org>:</p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>> I'm currently not in the mood to argue about VSTS' stability so I don't</p><p class=MsoNormal>>>> feel</p><p class=MsoNormal>>>> comfortable flipping that on as a requirement quite yet.</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> I don't suggest to make it mandatory right now.</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> I will try to keep on eye on VSTS ;-)</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> FWIW I had a quick look through the history of Windows commit builds on</p><p class=MsoNormal>> VSTS. There last three failures were:</p><p class=MsoNormal>> * test_subprocess getting wedged and the build timed out (surprisingly</p><p class=MsoNormal>> gracefully though, it sent a Ctrl+C to the app so we still got all the</p><p class=MsoNormal>> output)</p><p class=MsoNormal>> * Tcl/tk and/or OpenSSL build got stuck (this was on 3.6 - we don't build</p><p class=MsoNormal>> these every time as of 3.7)</p><p class=MsoNormal>> * test_asyncio issues</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Since the last of those issue, there have been 50-ish successful builds.</p><p class=MsoNormal>> (Note that I looked at commit builds, not PR builds, so I wouldn't have to</p><p class=MsoNormal>> wade through every single PR to see if it was a genuine bug.)</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> You can review the history here:</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Windows commits:</p><p class=MsoNormal>> https://python.visualstudio.com/cpython/_build/index?definitionId=4&_a=history&path=%5C</p><p class=MsoNormal>> Windows PRs:</p><p class=MsoNormal>> https://python.visualstudio.com/cpython/_build/index?definitionId=9&_a=history&path=%5C</p><p class=MsoNormal>> macOS commits:</p><p class=MsoNormal>> https://python.visualstudio.com/cpython/_build/index?definitionId=5&_a=history&path=%5C</p><p class=MsoNormal>> macOS PRs:</p><p class=MsoNormal>> https://python.visualstudio.com/cpython/_build/index?definitionId=8&_a=history&path=%5C</p><p class=MsoNormal>> Linux commits:</p><p class=MsoNormal>> https://python.visualstudio.com/cpython/_build/index?definitionId=6&_a=history&path=%5C</p><p class=MsoNormal>> Linux PRs:</p><p class=MsoNormal>> https://python.visualstudio.com/cpython/_build/index?definitionId=7&_a=history&path=%5C</p><p class=MsoNormal>> Linux with code coverage:</p><p class=MsoNormal>> https://python.visualstudio.com/cpython/_build/index?definitionId=13&_a=history&path=%5C</p><p class=MsoNormal>> (both commits and PRs right now, still undecided how to best make use of</p><p class=MsoNormal>> this run, as we don't seem to report coverage stats anywhere?)</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Cheers,</p><p class=MsoNormal>> Steve</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> _______________________________________________</p><p class=MsoNormal>> python-committers mailing list</p><p class=MsoNormal>> python-committers@python.org</p><p class=MsoNormal>> https://mail.python.org/mailman/listinfo/python-committers</p><p class=MsoNormal>> Code of Conduct: https://www.python.org/psf/codeofconduct/</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>