More principled tempdir usage by and between rustc, rustdoc and compiletest #138475
Labels
A-compiletest
Area: The compiletest test runner
A-test-infra
Area: test infrastructure (may span bootstrap/compiletest/more)
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-bug
Category: This is a bug.
E-needs-investigation
Call for partcipation: This issues needs some investigation to determine current status
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
"Specifically, it's somewhere here:
rust/compiler/rustc_codegen_ssa/src/back/link.rs
Lines 102 to 107 in cbfdf0b
"but yeah, in any case, we probably should override that, to point it under
build/test/$test_suite_name/$test_suite_revisioned_compare_moded/__temp/
"(E.g. by setting TMP_DIR/TEMP/TMP or whatever the env vars were called)
"Can you open an E-needs-investigation issue?" ~ @jieyouxu https://discord.com/channels/273534239310479360/957720175619215380/1349912066772963469
Spotted in #138157 (comment), the bors job failed with
It would be nice if those stayed in the
build
/target
directory, which is more likely to have a defender exclusion (and thus more likely to not have that access error). It would also be helpful to stay on the Dev Drive on Windows 11 if people have that set up, rather than useC:
which typically has the most extra filesystem access costs (from filters and such).And it'd just be nice not to have a bazillion of these left over after running tests a bunch :)
The text was updated successfully, but these errors were encountered: