-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: split x86_64-msvc job using windows 2025 #135632
base: master
Are you sure you want to change the base?
Conversation
@bors try |
…<try> [experiment] CI: split x86_64-msvc job using windows 2025 try-job: x86_64-msvc-1 try-job: x86_64-msvc-2
⌛ Trying commit b563fc9 with merge e8d81bcb17fe0d757c6e24a533de6f6e49bc6b3a... |
☀️ Try build successful - checks-actions |
good. It worked. Trying again to see if we were just lucky. @bors try |
…<try> [experiment] CI: split x86_64-msvc job using windows 2025 try-job: x86_64-msvc-1 try-job: x86_64-msvc-2
⌛ Trying commit b563fc9 with merge f5b8f99638fd7df176fd8a47a84352b50ea671c3... |
☀️ Try build successful - checks-actions |
Wooo. Let's test it again. @bors try |
…<try> [experiment] CI: split x86_64-msvc job using windows 2025 try-job: x86_64-msvc-1 try-job: x86_64-msvc-2
☀️ Try build successful - checks-actions |
@bors try |
…<try> [experiment] CI: split x86_64-msvc job using windows 2025 try-job: x86_64-msvc-1 try-job: x86_64-msvc-2
⌛ Trying commit b563fc9 with merge 42503c0eff91edd3c590358e274d0f112bb4c04e... |
☀️ Try build successful - checks-actions |
@bors try |
…<try> [experiment] CI: split x86_64-msvc job using windows 2025 try-job: x86_64-msvc-1 try-job: x86_64-msvc-2
☀️ Try build successful - checks-actions |
@bors try |
…<try> [experiment] CI: split x86_64-msvc job using windows 2025 try-job: x86_64-msvc-1 try-job: x86_64-msvc-2
☀️ Try build successful - checks-actions |
@bors try |
…<try> [experiment] CI: split x86_64-msvc job using windows 2025 try-job: x86_64-msvc-1 try-job: x86_64-msvc-2
☀️ Try build successful - checks-actions |
Considering, this appears to have a high success rate, this seems worth merging. |
Yes. There's another pr from me in the merge queue right now that touches this makefile. Once that PR is merged I'll update this PR and make it ready for review 👍 |
5f4864f
to
242b0e3
Compare
@bors try |
⌛ Trying commit 242b0e3 with merge 83f3740ecd05c200fc0412eb46bdb85980a13b34... |
…<try> CI: split x86_64-msvc job using windows 2025 try-job: x86_64-msvc-1 try-job: x86_64-msvc-2
☀️ Try build successful - checks-actions |
Let's try. @bors r+ rollup=never |
…Kobzol CI: split x86_64-msvc job using windows 2025 try-job: x86_64-msvc-1 try-job: x86_64-msvc-2
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
From my understanding, this should be a flaky error. |
@bors try |
…<try> CI: split x86_64-msvc job using windows 2025 try-job: x86_64-msvc-1 try-job: x86_64-msvc-2 try-job: dist-x86_64-msvc
⌛ Trying commit 242b0e3 with merge 53ba4de9d1f3e6cbdaef40d34463b16820572828... |
☀️ Try build successful - checks-actions |
windows-2025 seems to fix the flakiness discribed in #127883 — This PR never failed a
bors try
.This PR also removes the large runner by splitting it into two free runners, addressing rust-lang/infra-team#189 🥳
Too good to be true? Let's see! My suggestion is to merge this PR and observe how it behaves in the
auto
branch in the public dashboard over the following weeks.Additional context
I discussed this change in Zulip as well.
If you want to see a similar PR to this one where
x86_64-msvc
on windows 2022 fails in CI consistently, see #135483 (comment)r? @Kobzol
try-job: x86_64-msvc-1
try-job: x86_64-msvc-2
try-job: dist-x86_64-msvc