mirror of
https://github.com/astral-sh/uv
synced 2026-01-22 14:00:11 -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
58 lines
1.9 KiB
PowerShell
58 lines
1.9 KiB
PowerShell
# Configures a drive for testing in CI.
|
|
|
|
# When not using a GitHub Actions "larger runner", the `D:` drive is present and
|
|
# has similar or better performance characteristics than a ReFS dev drive.
|
|
# Sometimes using a larger runner is still more performant (e.g., when running
|
|
# the test suite) and we need to create a dev drive. This script automatically
|
|
# configures the appropriate drive.
|
|
|
|
# Note we use `Get-PSDrive` is not sufficient because the drive letter is assigned.
|
|
if (Test-Path "D:\") {
|
|
Write-Output "Using existing drive at D:"
|
|
$Drive = "D:"
|
|
} else {
|
|
# The size (20 GB) is chosen empirically to be large enough for our
|
|
# workflows; larger drives can take longer to set up.
|
|
$Volume = New-VHD -Path C:/uv_dev_drive.vhdx -SizeBytes 20GB |
|
|
Mount-VHD -Passthru |
|
|
Initialize-Disk -Passthru |
|
|
New-Partition -AssignDriveLetter -UseMaximumSize |
|
|
Format-Volume -DevDrive -Confirm:$false -Force
|
|
|
|
$Drive = "$($Volume.DriveLetter):"
|
|
|
|
# Set the drive as trusted
|
|
# See https://learn.microsoft.com/en-us/windows/dev-drive/#how-do-i-designate-a-dev-drive-as-trusted
|
|
fsutil devdrv trust $Drive
|
|
|
|
# Disable antivirus filtering on dev drives
|
|
# See https://learn.microsoft.com/en-us/windows/dev-drive/#how-do-i-configure-additional-filters-on-dev-drive
|
|
fsutil devdrv enable /disallowAv
|
|
|
|
# Remount so the changes take effect
|
|
Dismount-VHD -Path C:/uv_dev_drive.vhdx
|
|
Mount-VHD -Path C:/uv_dev_drive.vhdx
|
|
|
|
# Show some debug information
|
|
Write-Output $Volume
|
|
fsutil devdrv query $Drive
|
|
|
|
Write-Output "Using Dev Drive at $Volume"
|
|
}
|
|
|
|
$Tmp = "$($Drive)\uv-tmp"
|
|
|
|
# Create the directory ahead of time in an attempt to avoid race-conditions
|
|
New-Item $Tmp -ItemType Directory
|
|
|
|
Write-Output `
|
|
"DEV_DRIVE=$($Drive)" `
|
|
"TMP=$($Tmp)" `
|
|
"TEMP=$($Tmp)" `
|
|
"UV_INTERNAL__TEST_DIR=$($Tmp)" `
|
|
"RUSTUP_HOME=$($Drive)/.rustup" `
|
|
"CARGO_HOME=$($Drive)/.cargo" `
|
|
"UV_WORKSPACE=$($Drive)/uv" `
|
|
>> $env:GITHUB_ENV
|
|
|