-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Remove latest Windows SDK from 32-bit CI #137753
Conversation
@bors try |
[do not merge] Remove Win SDK 10.0.26100.0 from CI r? `@ghost` try-job: i686-msvc-1 try-job: i686-msvc-2 try-job: dist-i686-msvc
[do not merge] Remove Win SDK 10.0.26100.0 from CI r? `@ghost` try-job: i686-msvc-1 try-job: i686-msvc-2 try-job: dist-i686-msvc
This reverts commit 6ea4823.
6e629ad
to
f4a3eb6
Compare
f4a3eb6
to
2628424
Compare
This is ready to merge unless you want to wait for me figure out #137766. r? infra |
Could you please just add a comment on top of the step with a link to the tracking issue? Thanks! |
2628424
to
25617c7
Compare
Comment added! |
Thanks! Let's merge it preemptively, just in case GitHub updates the large runners soon. @bors r+ rollup=never |
This might be a bit more urgent @bors p=10 |
Do note that the tree is closed at priority 100. |
Lol, that sounds like a bors bug, it shouldn't even start to run CI on this PR. Thanks! @bors priority=101 |
@bors p=101 |
Ah, well, it's not a bors bug, because the tree got closed when CI for this PR was already running: #137775 (comment) |
The tree was closed after I did the priority bump so this just wasn't cancelled (which is good!) EDIT: ninja'd |
Ah, I forgot that it was a different tree closure, this situation is very dynamic =D |
BTW if |
It didn't in the try build but let's see |
Oh maybe it's because the Windows 2019 attempt is using a |
☀️ Test successful - checks-actions |
Finished benchmarking commit (2f58193): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (primary 1.3%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 772.925s -> 771.133s (-0.23%) |
[WIP] Revert "Remove Win SDK 10.0.26100.0 from CI" Part of rust-lang#137733. This reverts commit 25617c7, the remove-latest-windows-sdk workaround from rust-lang#137753. try-job: i686-msvc-1 try-job: i686-msvc-2 try-job: dist-i686-msvc
[beta] backports - Pass vendored sources from bootstrap to generate-copyright rust-lang#137020 - Fix `-win7-windows-msvc` target since 26eeac1* rust-lang#137270 - skip submodule updating logics on tarballs rust-lang#137338 - Improve behavior of `IF_LET_RESCOPE` around temporaries and place expressions rust-lang#137444 - downgrade bootstrap `cc` rust-lang#137460 - Remove latest Windows SDK from 32-bit CI rust-lang#137753 - [beta-1.86] Ensure we can package directories ending with '.rs' (rust-lang/cargo#15248) rust-lang#137842 r? cuviper
Revert "Remove Win SDK 10.0.26100.0 from CI" Part of rust-lang#137733. Resolves rust-lang#137733. The remove-latest-windows-sdk workaround workaround should no longer be necessary, now that we bumped (1) cargo `cc` and (2) `rustc_{codegen_ssa,llvm}` `cc`. This reverts commit 25617c7, the remove-latest-windows-sdk workaround from rust-lang#137753. try-job: i686-msvc-1 try-job: i686-msvc-2 try-job: dist-i686-msvc
This is an alternative to #137766, in case that doesn't work. It is in some ways simpler but is less principled and may be more flaky (as it involves deleting stuff).
try-job: i686-msvc-1
try-job: i686-msvc-2
try-job: dist-i686-msvc