t 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.do...@py
Hah, yes, that was un-intuitive for me. I was looking for something
labelled "logs" to click on. thanks. (I hope MS is taking notes on UX
issues here)
So these failures were in fact the known flakes and not infrastructure.
good!
On the high level view of VSTS output on a failure:
"Issues:
On Fri, May 18, 2018 at 1:13 PM, Steve Dower 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
On 5/18/2018 4:13 PM, Steve Dower wrote:
Close/reopen PR is the best way to trigger a rebuild right now.
It may be the way to retrigger VSTS, but if one want to merge, and
either of Travis or AppVeyor pass, tossing the success is a foolish
thing to do. Either may fail on a rebuild.
--
On Fri, May 18, 2018 at 4:15 PM Steve Dower wrote:
[..]
> 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
most steps – I’m happy to add
that in if someone can help with the right git incantation.
Top-posted from my Windows phone
From: Zachary Ware
Sent: Friday, May 18, 2018 9:15
To: Python-Dev
Subject: Re: [Python-Dev] please help triage VSTS failures
On Fri, May 18, 2018 at 10:55 AM, Gregory P
On Fri, May 18, 2018 at 10:55 AM, Gregory P. Smith wrote:
> These both look like VSTS infrastructure falling over on PRs:
>
> https://python.visualstudio.com/cpython/_build?buildId=522
>
> https://python.visualstudio.com/cpython/_build?buildId=523
>
> I don't see anywhere that