classification
Title: VSTS: Initialize phase: failed
Type: Stage: resolved
Components: Tests Versions: Python 3.8
process
Status: closed Resolution: duplicate
Dependencies: Superseder: VSTS Windows-PR: internal error
View: 33782
Assigned To: Nosy List: brett.cannon, eric.snow, steve.dower, vstinner
Priority: normal Keywords:

Created on 2018-06-20 12:30 by vstinner, last changed 2018-06-20 15:44 by vstinner. This issue is now closed.

Messages (4)
msg320072 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2018-06-20 12:30
Just one example:

VSTS: Linux-PR — Linux-PR_20180620.24 failed:
https://python.visualstudio.com/cpython/cpython%20Team/_build/results?buildId=11119&view=logs

"Initialize phase: failed"

"""
2018-06-20T12:20:59.9720705Z ##[section]Starting: Expand phase phase1
2018-06-20T12:20:59.9876970Z Execution:
2018-06-20T12:20:59.9876970Z   MaxConcurrency:
2018-06-20T12:20:59.9876970Z     Default Value: 1
2018-06-20T12:20:59.9876970Z ##[section]Finishing: Expand phase phase1
"""
msg320073 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2018-06-20 12:32
See also bpo-33782 "VSTS Windows-PR: internal error".
msg320082 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2018-06-20 15:36
Considering all we can do is pass the reports onto the team (which I've been doing), there's no point repeatedly opening new issues for the same problem.
msg320084 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2018-06-20 15:44
Oh, you think that it's the same bug? The result page looked different, so I opened a different bug report.
History
Date User Action Args
2018-06-20 15:44:44vstinnersetmessages: + msg320084
2018-06-20 15:36:38steve.dowersetstatus: open -> closed
stage: resolved
2018-06-20 15:36:32steve.dowersetsuperseder: VSTS Windows-PR: internal error
resolution: duplicate
messages: + msg320082
2018-06-20 12:32:04vstinnersetmessages: + msg320073
2018-06-20 12:30:21vstinnercreate