Author vstinner
Recipients brett.cannon, miss-islington, ned.deily, python-dev, steve.dower, vstinner
Date 2020-04-01.12:53:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1585745593.64.0.878382400166.issue39837@roundup.psfhosted.org>
In-reply-to
Content
I cannot merge a PR until it completes. It re-runs jobs which are already run as GH Actions.

There is another annoying issue with Azure Pipelines. When a job fails randomly for whatever reason, a job cannot be re-run, even if I log in Microsoft Azure.

Usually, the workaround is to close/reopen a PR to re-run all CIs.

Except that for a backport PR created automatically by miss-islington bot, when I close the PR, the bot removes its branch and so the PR cannot be re-open.

Well, the second workaround is to ask the bot to create a new PR backport. That what I did.

I did that for PR 19276 of bpo-40121. It's annoying to have to use *two* workarounds.

On the other side, Travis CI is not currently required, I don't understand why.

Is it possible to make Travis CI required and make Azure Pipelines not required?
History
Date User Action Args
2020-04-01 12:53:13vstinnersetrecipients: + vstinner, brett.cannon, ned.deily, python-dev, steve.dower, miss-islington
2020-04-01 12:53:13vstinnersetmessageid: <1585745593.64.0.878382400166.issue39837@roundup.psfhosted.org>
2020-04-01 12:53:13vstinnerlinkissue39837 messages
2020-04-01 12:53:13vstinnercreate