<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>Unfamiliar maybe, though I’m a big fan of separating build and test logs. If anyone is motivated enough to make unittest/regrtest generate Junit format XML then we can get a nice breakdown by individual test, too, which would save scrolling through the log entirely.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU>The asyncio instability is apparently really hard to fix. There were 2-3 people looking into it yesterday on one of the other systems, but apparently we haven’t solved it yet (my guess is lingering state from a previous test). The multissl script was my fault for not realising that we don’t use it on 3.6 builds, but that should be fixed already. Close/reopen PR is the best way to trigger a rebuild right now.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU>According to the VSTS dev team, an easy “rerun this build” button and filtering by changed paths are coming soon, which should clean things up. We *<b>could</b>* add our own detection for doc-only changes and skip most steps – I’m happy to add that in if someone can help with the right git incantation.</span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Top-posted from my Windows 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:zachary.ware+pydev@gmail.com">Zachary Ware</a><br><b>Sent: </b>Friday, May 18, 2018 9:15<br><b>To: </b><a href="mailto:python-dev@python.org">Python-Dev</a><br><b>Subject: </b>Re: [Python-Dev] please help triage VSTS failures</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On Fri, May 18, 2018 at 10:55 AM, Gregory P. Smith <greg@krypto.org> wrote:</p><p class=MsoNormal>> These both look like VSTS infrastructure falling over on PRs:</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> https://python.visualstudio.com/cpython/_build?buildId=522</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> https://python.visualstudio.com/cpython/_build?buildId=523</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> I don't see anywhere that gives information about the failures. (*)</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Somewhat non-intuitively, logs are available by clicking something in</p><p class=MsoNormal>the tree in the left column (in particular, the inner-most thing with</p><p class=MsoNormal>a red X). Do be sure to choose "Logs" in the right pane rather than</p><p class=MsoNormal>"Tests"; "Tests" appears to be a separate feature that we don't use.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> These CI failures on different platforms are both for the same change, on</p><p class=MsoNormal>> different branches, for a documentation only change. That passed on the</p><p class=MsoNormal>> other branches and platforms for the same change.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The Windows failure appears to be the test_asyncio instability that</p><p class=MsoNormal>has been popping up everywhere the past couple of days. The Linux</p><p class=MsoNormal>failure looks like a mis-use of Tools/ssl/multissltests.py in the</p><p class=MsoNormal>setup, but I thought I'd seen a checkin go by that removed that.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-- </p><p class=MsoNormal>Zach</p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>Python-Dev mailing list</p><p class=MsoNormal>Python-Dev@python.org</p><p class=MsoNormal>https://mail.python.org/mailman/listinfo/python-dev</p><p class=MsoNormal>Unsubscribe: https://mail.python.org/mailman/options/python-dev/steve.dower%40python.org</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>