user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

add comment explaining the test_build_dir

Browse source
This commit is contained in:
bit-aloo 2025-09-22 18:54:23 +05:30
parent 8a0e3808c0
commit 83b784fda1
No known key found for this signature in database
1 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
src/bootstrap/src/core/config/config.rs
View file

@ -2479,6 +2479,13 @@ fn find_correct_section_for_field(field_name: &str) -> Vec<WouldBeValidFor> {
.collect()
}
/// Resolve the build directory used for tests.
///
/// - When tests are run through bootstrap (`x.py test`), the build system
/// sets `CARGO_TARGET_DIR`, so we can trust and use it here.
/// - When tests are run directly with cargo test, `CARGO_TARGET_DIR` will
/// not be set. In that case we fall back to resolving relative to
/// `CARGO_MANIFEST_DIR`, by walking two parents up and appending `build`.
fn test_build_dir() -> PathBuf {
env::var_os("CARGO_TARGET_DIR")
.map(|value| Path::new(&value).parent().unwrap().to_path_buf())