@aeros and @terryjreedy: Status check is done, and it's a success ✅ .

Sorry, I can't merge this PR. Reason: Required status check "Azure Pipelines PR" is expected..

@Mariatta Getting both 'status check passed' and 'status check failed' (paraphrased in both cases) is confusing. Without a link to the Azure Pipelines details, I cannot check the latter. This is the second try for 3.8. #16885 was the first. Backports for 3.7 #16886 and 2.7 #16888 went routinely.

I think it's safe to say that a minor link fix in the docs shouldn't be causing issues in Azure, particularly since it passed in the other branches without a problem. From what it looks like, it seems to be a configuration issue in Azure Pipelines for the 3.8 branch. Particularly since there's no status report after 12 hours.

I'll try to close and reopen this PR to trigger the tests again, the issue may have been fixed from the time the PR was opened.

@aeros and @terryjreedy: Status check is done, and it's a success ✅ .

Sorry, I can't merge this PR. Reason: Required status check "Azure Pipelines PR" is expected..

Sorry, I can't merge this PR. Reason: 2 of 5 required status checks have not succeeded: 1 expected and 1 pending..

@aeros and @terryjreedy: Status check is done, and it's a failure ❌ .

@terryjreedy Oops, looks like that deleted the backport. I wasn't aware that miss islington could do that and have yet to see anything like this, I'm used to using the close and reopen to retrigger the tests in non-backport PRs (normally the backports have gone more smoothly). The spam of different and repeated check messages seem rather unusual, it's usually just a single message.

I can reopen a new one manually if needed, let me know. Sorry about that.

Edit: Looks like miss islington attempted to open another backport PR: #16895 (Mariatta might have done that). Azure is correctly running on that one.

I can close and retrigger tests on a new PR by adding the backport label (again) to the original PR.

@terryjreedy

I can close and retrigger tests on a new PR by adding the backport label (again) to the original PR.

Oh that's good to know, I wasn't aware of that functionality.

It looks like it was resolved by Mariatta for the 3.8 branch with #16895. Were there any other backports that had issues?

I have occasionally in the past had more trouble with 3.8 than with 3.7. If you are interested, check whether and how 3.8 CI setup is different from 3.7. With 3.8.0 out, I expect that they should be the same.