Maybe worth implementing a `retest` command so our bots can retrigger the tests without closing PR. Jenkins has this command. ᐧ
On Tue, May 21, 2019 at 8:40 PM Steve Dower <steve.do...@python.org> wrote: > Close/reopen is still the easiest way, unfortunately. I've been bugging > the team to improve this, but other priorities have been higher. > > And I see this is a backport, which means as soon as you close it > miss-islington will delete the branch and there's no way to restart it. > > If we integrated Pipelines through the GitHub app then it would have a > "re-run check" button. I haven't done that yet as I don't have > permissions to update our GitHub org and haven't forced someone who does > to sit down and do it with me :) > > For those of us who can log in (GitHub auth integration is also delayed, > so it's manual user management right now) there should be a "Rebuild" > button in the new UI, but that's missing on your build for some reason. > I'll ping some people to find out. > > Cheers, > STeve > > On 21May2019 1110, Antoine Pitrou wrote: > > > > Hello, > > > > How can I restart a failed build on Azure? > > > https://dev.azure.com/Python/cpython/_build/results?buildId=43161&view=logs&j=18d1a34d-6940-5fc1-f55b-405e2fba32b1 > > > > Regards > > > > Antoine. > > _______________________________________________ > 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/ >
_______________________________________________ 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/
