3 Commits

Author	SHA1	Message	Date
Zanie Blue	75a1a47859	Improve performance of our test drive in Windows CI (#10651) ... Previously, we couldn't use a DevDrive (https://github.com/astral-sh/uv/pull/3522#issuecomment-2111448930) because our Windows version was not sufficient. Recently, I upgraded our larger runners to Windows 2025 preview (https://github.com/astral-sh/uv/pull/10298) which I presume has support for this. I removed ReFS in https://github.com/astral-sh/uv/pull/10651/commits/953c3535c3754f580ecd8da55637756f58606567 which didn't seem to do anything to performance. I also found some notes on "trusted" DevDrives and "disabling anti-virus filtering" which I simply have to try.	2025-01-16 12:07:09 -06:00
Zanie Blue	47eeef5c09	Explicitly create the DevDrive tmpdir before use (#7644) ... A suggested solution to #6940 — unfortunately only time will tell if it works.	2024-09-23 12:59:22 -05:00
Amos Wenger	3e207da3bc	ci(windows): Introduce setup-dev-drive.ps1, maximize dev drive usage (#6858) ... As suggested by @samypr100 on #6680: https://github.com/astral-sh/uv/pull/6680#issuecomment-2313607984 ## Summary Instead of using `UV_INTERNAL__TEST_DIR`, it simply exports `TEMP` when running Windows jobs. ## Test Plan I'm going to run this manually under ProcMon on my Windows machine and see where uv writes temp files, hopefully to the dev drive and not `%(LOCAL)APPDATA%` or something. I'm going to commit a dummy code change and look at build time changes in CI.	2024-08-30 08:54:25 -04:00