First run did not exhibit timeout. Force push to rerun CI. Let's check whether this is reliable by running CI multiple times.

Second run did not exhibit timeout. Force push to rerun CI.

This did not have timeouts three times in a row.

I suggest to merge this and see whether our timouts are gone. We would have to update the image in a month anyway due to the deprecation, and I don't think it's a relevant miss if we don't run the windows-2019 image.

There is an if-loop at line 123 that the comment states is for windows-2019. I guess that can be removed.

I'm guessing but not 100% this wants to be backported, so I've milestoned for that on the basis that it's easier to have the backports opened and close them if not wanted than having to manually backport.

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout v3.10.xgit pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 ab102c079ae0474861bbb1dcc64da436d1a84f8b

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #29992: Update pinned oldest win image on azure'

4. Push to a named branch:

git push YOURFORK v3.10.x:auto-backport-of-pr-29992-on-v3.10.x

5. Create a PR against branch v3.10.x, I would have named this PR:

"Backport PR#29992 on branch v3.10.x (Update pinned oldest win image on azure)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove theStill Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free tosuggest an improvement.

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout v3.10.1-docgit pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 ab102c079ae0474861bbb1dcc64da436d1a84f8b

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #29992: Update pinned oldest win image on azure'

4. Push to a named branch:

git push YOURFORK v3.10.1-doc:auto-backport-of-pr-29992-on-v3.10.1-doc

5. Create a PR against branch v3.10.1-doc, I would have named this PR:

"Backport PR#29992 on branch v3.10.1-doc (Update pinned oldest win image on azure)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove theStill Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free tosuggest an improvement.

Note: This seems not to fix it completely. This is a run with windows-2022 and it still produces a timeout. 😢

https://dev.azure.com/matplotlib/matplotlib/_build/results?buildId=43805&view=logs&j=f92c32cd-721a-536e-3a87-a0c010db3f7f&t=18f30b55-1017-4d18-b8e0-646f3513b769

I'm not yet taking any further action, like repoening#29981, yet. Let's monitor the situation further.