<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>Hmm... I would guess that it would create a new "build” and likely lose the link to the original (though it would still be kept, just harder to find). Then again, the existing support for rerunning a release through VSTS keeps all the previous attempts... I’ll mention it, but the quickest fix here may not be immediately sufficient.</span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent 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:njs@pobox.com">Nathaniel Smith</a><br><b>Sent: </b>Friday, May 18, 2018 17:34<br><b>To: </b><a href="mailto:steve.dower@python.org">Steve Dower</a><br><b>Cc: </b><a href="mailto:zachary.ware+pydev@gmail.com">Zachary Ware</a>; <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 1:13 PM, Steve Dower <steve.dower@python.org> wrote:</p><p class=MsoNormal>> According to the VSTS dev team, an easy “rerun this build” button and</p><p class=MsoNormal>> filtering by changed paths are coming soon, which should clean things up.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If you're talking to them, please ask them to make sure that the</p><p class=MsoNormal>"rerun this build" button doesn't erase the old log. (That's what it</p><p class=MsoNormal>does on Travis. Appveyor is better.) The problem is that when you have</p><p class=MsoNormal>a flaky/intermittent failure, your todo list is always (a) rerun the</p><p class=MsoNormal>build so at least it's not blocking whatever this unrelated change is,</p><p class=MsoNormal>(b) file some sort of bug, or comment on some existing bug, and link</p><p class=MsoNormal>to the log to help track down the intermittent failure. If you click</p><p class=MsoNormal>the "rebuild" button on Travis, then it solves (a), while deleting the</p><p class=MsoNormal>information you need for (b) – and for rare intermittent bugs you</p><p class=MsoNormal>might not have much information to go on besides that build log.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-n</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-- </p><p class=MsoNormal>Nathaniel J. Smith -- https://vorpus.org</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>