Cirrus Runners was purchased by OpenAI, which promptly shut it down (dig cirrus-runners.app is empty).
So temporarily move the runners from OpenAI to Microsoft.
Cirrus Runners was purchased by OpenAI, which promptly shut it down (dig cirrus-runners.app is empty).
So temporarily move the runners from OpenAI to Microsoft.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
If your review is incorrectly listed, please copy-paste <code><!--meta-tag:bot-skip--></code> into the comment that the bot should ignore.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
LLM disclaimer: This diff was written by OpenAI Codex
I thought they were supposed to keep going until June 1, but it looks like the runners are gone... All current CI tasks that used their runners are stuck on "waiting for a runner".
ACK fa43cfdd7271f05aa27d05851cdca5321e956b9f
Yeah, idk either. I can also only see that it is down, but we'll have to do the switch anyway, and this is just a temporary workaround.
If the CI passes here, but not otherwise, it seems fine to merge, but should also be fine to wait longer.
timed out ...
timed out ...
Interesting as it has been working on forks. I wonder if a primed cache would have helped. I see you have updated the timeouts now which seems reasonable.
Concept ACK, even if this only a very temporary solution. Things will back up and be very slow but some runs is better than no runs.
ACK fae494ab6d2eab1e5646236f74aa09c7bd66877f - With the understanding that Cirrus Runners are unavailable