Use a larger runner for Windows#396

Open

CleanCut wants to merge 18 commits intomainfrom

cleancut/windows-larger-runner

Commits on Mar 27, 2026

use a larger runner that Josh configured for Windows
CleanCut
committed
the larger runner apparently doesn't have a D: drive
CleanCut
committed
make it explicit we use Swatinem/rust-cache through the setup-rust-toolchain action; add more config options
CleanCut
committed
do all test builds with the test profile so we stop recompiling so much
CleanCut
committed
use Rust's lld linker on Windows
CleanCut
committed
have oxen-py use the glob from the workspace
CleanCut
committed
the test profile doesn't produce symbols for Python to use, so have everything use the dev profile instead
CleanCut
committed
use the latest version of each runner to avoid Node 20 vs 24 warnings
CleanCut
committed
try using a ramdisk on windows for cargo target dir and oxen data dirs
CleanCut
committed
narrow the windows oxen-server ramdisk usage to data/test/runs
CleanCut
committed
avoid using a junction; instead use an env var to point oxen-server to the ramdisk
CleanCut
committed
cache cargo build artifacts on the ramdisk in windows
CleanCut
committed
use a virtual hard drive file on the ramdisk to provide full NTFS compatibility in order to build libduckdb-sys
CleanCut
committed
try bumping the size of the ramdisk and virtual hard drive
CleanCut
committed
add configuration to store test temp files on the vhd in windows ci
CleanCut
committed
use the same canonicalization in all the places--it spits out a different syntax on a windows vhd
CleanCut
committed

Commits on Mar 28, 2026