Right now, close/reopen the PR is the easiest way. :(

test_asyncio sometimes still fail randomly on Travis CI or AppVeyor: https://bugs.python.org/issue33694

If I close/reopen the PR, I take the risk of getting a failure on a differrent CI :-)

Victor

2018-06-06 16:13 GMT+02:00 Steve Dower steve.dower@python.org:

Right now, close/reopen the PR is the easiest way. :( Even with login, it’s not so easy to restart a GitHub PR build because the integration isn’t fully there yet (I think you can only do it through the API and not the UI). I’m assured it’s coming – this was top of my list of “things we need” that I sent to the VSTS team.

Top-posted from my Windows 10 phone

From: Victor Stinner Sent: Wednesday, June 6, 2018 6:45 To: python-committers Subject: [python-committers] VSTS: how to rebuild a failing build?

Hi,

While we are discussing to make VSTS mandatory, I have a question: how

can I schedule a rebuild when VSTS failed (and the failure is

unrelated to my change)?

I'm logged in, but I don't see any action button on:

https://python.visualstudio.com/cpython/_build?buildId=6469

I guess that I lack some permissions. I clicked on at top right (on

"(VS)") -> "My profile" but I get an error :-) I cannot see my own

profile:

https://python.visualstudio.com/_details/profile/redirect

"Sorry, but Victor Stinner victor.stinner@gmail.com (Microsoft

account) is not authorized to access this page"

Note: the Windows-PR build failed because of an "internal error".

Steve Dower already passed the bug to the right people.

https://bugs.python.org/issue33782

Victor

---

python-committers mailing list

python-committers@python.org

https://mail.python.org/mailman/listinfo/python-committers

Code of Conduct: https://www.python.org/psf/codeofconduct/