mirror of
https://github.com/astral-sh/uv
synced 2026-01-20 21:10:10 -05:00
896435faec
When using the standard Windows runners (as opposed to the _larger_ GitHub runners), an undocumented `D:` drive is available and performant. We can save some money on by using this on a standard runner instead of a larger runner with an ReFS drive. Switching to the `D:` drive was not acceptable for `cargo test` >25m runtime. Inspired by https://github.com/pypa/pip/pull/13129 See https://github.com/actions/runner-images/issues/8755 Timings (grain of salt — GitHub is super noisy): - clippy: 2m 18s -> 2m 11s - build binary: 2m 3s -> 2m 35s - trampoline check (x86-64): 2m 32s -> 1m 50s (other architectures similar) - trampoline test (x86-64): 4m 12s -> 6m 7s - trampoline test (i686): 6m 44s -> 5m 35s