[Python-Dev] please help triage VSTS failures (original) (raw)

Steve Dower steve.dower at python.org
Fri May 18 16:13:25 EDT 2018

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.

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.

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 could 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.

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. Smith <greg at krypto.org> 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 gives information about the failures. (*)

Somewhat non-intuitively, logs are available by clicking something in the tree in the left column (in particular, the inner-most thing with a red X). Do be sure to choose "Logs" in the right pane rather than "Tests"; "Tests" appears to be a separate feature that we don't use.

These CI failures on different platforms are both for the same change, on different branches, for a documentation only change. That passed on the other branches and platforms for the same change.

The Windows failure appears to be the test_asyncio instability that has been popping up everywhere the past couple of days. The Linux failure looks like a mis-use of Tools/ssl/multissltests.py in the setup, but I thought I'd seen a checkin go by that removed that.

-- Zach

Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/steve.dower%40python.org

-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180518/3dd08165/attachment.html>

More information about the Python-Dev mailing list