konsti/clear-env-for-tests - Branch - astral-sh/uv

astral-sh

Blog Docs Changelog

Clear the env vars for tests

#14080

Comparing

konsti/clear-env-for-tests

(

c7e4f78

) with

main

(

ea5a092

)

-1%

Untouched: 6

Benchmarks

Passed

resolve_warm_jupyter_universal

crates/uv-bench/benches/uv.rs::uv::resolve_warm_jupyter_universal

204 ms203.4 ms

resolve_warm_jupyter

crates/uv-bench/benches/uv.rs::uv::resolve_warm_jupyter

69.2 ms69.2 ms

resolve_warm_jupyter_universal

crates/uv-bench/benches/uv.rs::uv::resolve_warm_jupyter_universal

134.8 ms135.2 ms

resolve_warm_airflow

crates/uv-bench/benches/uv.rs::uv::resolve_warm_airflow

-1%

760.2 ms765.1 ms

resolve_warm_airflow

crates/uv-bench/benches/uv.rs::uv::resolve_warm_airflow

-1%

433.7 ms439.7 ms

resolve_warm_jupyter

crates/uv-bench/benches/uv.rs::uv::resolve_warm_jupyter

-2%

39.2 ms39.9 ms

Commits

Click on a commit to change the comparison range

Base

main

ea5a092

-0.18%

Clear the env vars for tests Currently, it's possible to break our test suite by having an env var set that influences uv, either a `UV_*` var, or something more generic such as the XDG env vars. We previously fixed them env-var-by-env-var as we discovered. By clearing the env var for subcommands entirely, we can invert this to only include the env vars we care about. Notable limitations are that this only affects tests that use `TestContext::add_shared_env` (default, can be opted-out) and we still pass a (modified) `PATH`.

92a469b

4 months ago

by konstin

-0.45%

c7e4f78

6 hours ago

by konstin

Home Terms Privacy Docs