Tracking Issue for insufficient disk space on x86_64-msvc-* CI jobs due to broken Windows Server 2025 20250504.1.0 images
#141022
Labels
A-CI
Area: Our Github Actions CI
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
Comments
jieyouxu
added
T-infra
This was referenced May 15, 2025
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
May 15, 2025
…=marcoieni Temporarily use Windows Server 2022 instead of Windows Server 2025 images Tracking issue: rust-lang#141022 At the moment, it seems like Windows Server 2025 20250504.1.0 is misconfigured, causing insufficient disk space failures. Temporarily go back to Windows Server 2022 in the hope that those are not also misconfigured to try to unblock the queue. r? `@marcoieni` (or infra-ci)
jieyouxu
changed the title
x86_64-msvc-1 CI failurex86_64-msvc-* CI jobs due to broken Windows Server 2025 20250504.1.0 images
rust-bors bot
added a commit
that referenced
this issue
Jun 1, 2025
[WIP] Switch `x86_64-msvc-{1,2}` back to Windows Server 2025 images
New Windows Server 2025 images have been released (20250527).
Let's try if the newer Windows Server 2025 exhibit lack of disk space problem or not, cf. #141022.
r? `@ghost`
try-job: `x86_64-msvc-*`
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jun 2, 2025
…527, r=Kobzol
Switch `x86_64-msvc-{1,2}` back to Windows Server 2025 images
New Windows Server 2025 images have been released (**20250527.1.0**). New images appear to not exhibit the lack-of-disk-space problem as tracked by rust-lang#141022, and the new runner image's storage capacity appears to be configured correctly.
Windows Server 2025 image version **20250527.1.0** release notes: <https://github.com/actions/runner-images/releases/tag/win25%2F20250527.1>.
Resolves rust-lang#141022.
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jun 2, 2025
…527, r=Kobzol
Switch `x86_64-msvc-{1,2}` back to Windows Server 2025 images
New Windows Server 2025 images have been released (**20250527.1.0**). New images appear to not exhibit the lack-of-disk-space problem as tracked by rust-lang#141022, and the new runner image's storage capacity appears to be configured correctly.
Windows Server 2025 image version **20250527.1.0** release notes: <https://github.com/actions/runner-images/releases/tag/win25%2F20250527.1>.
Resolves rust-lang#141022.
rust-timer
added a commit
that referenced
this issue
Jun 3, 2025
Rollup merge of #141861 - jieyouxu:windows-server-2025-20250527, r=Kobzol Switch `x86_64-msvc-{1,2}` back to Windows Server 2025 images New Windows Server 2025 images have been released (**20250527.1.0**). New images appear to not exhibit the lack-of-disk-space problem as tracked by #141022, and the new runner image's storage capacity appears to be configured correctly. Windows Server 2025 image version **20250527.1.0** release notes: <https://github.com/actions/runner-images/releases/tag/win25%2F20250527.1>. Resolves #141022.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Date range: 2025-05-14 - 2025-06-01
Summary
We're observing the Windows Server 2025 image (specifically 20250504.1.0) appears to have some configuration problems, causing insufficient disk space.
Discussions and upstream report
windows-2025jobs started failing because "not enough space on the disk" actions/runner-images#12199Mitigation attempts
Resolution
x86_64-msvc-{1,2}back to Windows Server 2025 images #141861The text was updated successfully, but these errors were encountered: