aarch64-darwin Hydra builder: insufficient disk space for dotnet-vmr-10.0.3 build

[helgeu]

Problem

The aarch64-darwin Hydra builder runs out of disk space when building dotnet-stage0-vmr-10.0.3, preventing dotnetCorePackages.sdk_10_0 from being cached for aarch64-darwin since March 8, 2026.

Evidence

Hydra build #323311985 fails with:

tar: dotnet-10.0.103/test: Cannot mkdir: No space left on device
tar: Exiting with failure status due to previous errors
do not know how to unpack source archive /nix/store/m1f8w9bk9cnnfv79wc5j8jsf796nb7bv-v10.0.103.tar.gz

The failure occurs during source extraction — before the build even starts. The .NET VMR tarball is large and the builder's disk cannot accommodate it.

• Last successful build: #322283876 (Feb 24, 2026)
• Failing since: #323311985 (March 8, 2026)
• Hydra job: https://hydra.nixos.org/job/nixpkgs/trunk/dotnetCorePackages.sdk_10_0.aarch64-darwin
• Builder machine: enormous-catfish

Impact

No cached binary for sdk_10_0 on aarch64-darwin. Users on nixpkgs-unstable who include this package get stuck in a multi-hour local VMR source build that may also fail due to disk constraints.

Related

• dotnetCorePackages.sdk_10_0: Hydra build fails on aarch64-darwin (disk space exhaustion) nixpkgs#500454 — build failure issue filed on nixpkgs

Suggested Fix

Increase disk allocation on the enormous-catfish aarch64-darwin builder (or whichever machine handles this job), and retrigger the build.

[vcunat]

It seems building OK since then:
https://hydra.nixos.org/job/nixpkgs/unstable/dotnetCorePackages.sdk_10_0.aarch64-darwin