[Python-Dev] please help triage VSTS failures
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.
Sent from my Windows 10 phone
From: Nathaniel Smith
Sent: Friday, May 18, 2018 17:34
To: Steve Dower
Cc: Zachary Ware; Python-Dev
Subject: Re: [Python-Dev] please help triage VSTS failures
On Fri, May 18, 2018 at 1:13 PM, Steve Dower <steve.dower at python.org> wrote:
> 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.
If you're talking to them, please ask them to make sure that the
"rerun this build" button doesn't erase the old log. (That's what it
does on Travis. Appveyor is better.) The problem is that when you have
a flaky/intermittent failure, your todo list is always (a) rerun the
build so at least it's not blocking whatever this unrelated change is,
(b) file some sort of bug, or comment on some existing bug, and link
to the log to help track down the intermittent failure. If you click
the "rebuild" button on Travis, then it solves (a), while deleting the
information you need for (b) ? and for rare intermittent bugs you
might not have much information to go on besides that build log.
Nathaniel J. Smith -- https://vorpus.org
-------------- next part --------------
An HTML attachment was scrubbed...