[issue33782] VSTS Windows-PR: internal error

Change by Steve Dower : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-l

[issue33782] VSTS Windows-PR: internal error

Steve Dower added the comment: > A quick follow-up commit can happen if one uses the web editor to edit more > than one file I hadn't thought of that one. Hopefully they'll just fix their bug though :) I spent a bit of time at the EuroPython sprints making the changes to quickly finish the

[issue33782] VSTS Windows-PR: internal error

Terry J. Reedy added the comment: A quick follow-up commit can happen if one uses the web editor to edit more than one file. Editing a news file in Misc/News/next should not trigger any of the normal tests, only a blurb check if there is such. -- nosy: +terry.reedy

[issue33782] VSTS Windows-PR: internal error

Steve Dower added the comment: It appears to be a known issue when a PR is retriggered (due to new commits) early enough in the CI run. I haven't got any info about when it'll be fixed. -- ___ Python tracker __

[issue33782] VSTS Windows-PR: internal error

STINNER Victor added the comment: Steve: hi! Any update on the Microsoft side? -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue33782] VSTS Windows-PR: internal error

Steve Dower added the comment: Right. This build failed to start, which is why there's only one section on the left hand side (normally you'll see all the build steps there, and clicking on them will show their logs). I think it'll be an internal race condition. I'll pass back whatever info

[issue33782] VSTS Windows-PR: internal error

STINNER Victor added the comment: > The "build not retained" state just means it'll get cleaned up after seven > days. Oh ok. But I'm confused, I don't see where are the logs. I clicked on Timeline, Code coverage, Tests: all are empty. In the logs ZIP, I cannot see any command related to Py

[issue33782] VSTS Windows-PR: internal error

Steve Dower added the comment: I'd already started discussing this with the VSTS team, it seems to be a bug on their side. The "build not retained" state just means it'll get cleaned up after seven days. People with login access can mark a build to be kept permanently, which changes that st

[issue33782] VSTS Windows-PR: internal error

Change by STINNER Victor : -- assignee: -> steve.dower ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue33782] VSTS Windows-PR: internal error

STINNER Victor added the comment: By the way, it seems like tests were not run on the Linux-PR job: https://python.visualstudio.com/cpython/_build?buildId=6467&tab=summary&_a=summary Linux-PR / Build Linux-PR_20180606.13: "No test runs are available for this build." "Retained state Build no

[issue33782] VSTS Windows-PR: internal error

New submission from STINNER Victor : On my PR https://github.com/python/cpython/pull/7447 "VSTS: Windows-PR" failed: "Windows-PR_20180606.13 failed". https://python.visualstudio.com/cpython/_build?buildId=6469 "The request was failed due to an internal service error. Please try again." -