-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run-make-support: rename tmp_dir()
and clarify its semantics
#125726
Labels
A-docs
Area: Documentation for any part of the project, including the compiler, standard library, and tools
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-bug
Category: This is a bug.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
In #125827 we named the output artifacts directory |
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jun 8, 2024
Change how runmake v2 tests are executed This PR makes execution of v2 runmake tests more sane, by executing each test in a temporary directory by default, rather than running it inside `tests/run-make`. This will have.. a lot of conflicts. Fixes: rust-lang#126080 Closes rust-lang#125726, because it removes `tmp_dir`, lol. r? `@jieyouxu`
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jun 8, 2024
Change how runmake v2 tests are executed This PR makes execution of v2 runmake tests more sane, by executing each test in a temporary directory by default, rather than running it inside `tests/run-make`. This will have.. a lot of conflicts. Fixes: rust-lang#126080 Closes rust-lang#125726, because it removes `tmp_dir`, lol. r? `@jieyouxu`
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jun 8, 2024
Change how runmake v2 tests are executed This PR makes execution of v2 runmake tests more sane, by executing each test in a temporary directory by default, rather than running it inside `tests/run-make`. This will have.. a lot of conflicts. Fixes: rust-lang#126080 Closes rust-lang#125726, because it removes `tmp_dir`, lol. r? `@jieyouxu` try-job: x86_64-msvc
flip1995
pushed a commit
to flip1995/rust-clippy
that referenced
this issue
Jun 28, 2024
Change how runmake v2 tests are executed This PR makes execution of v2 runmake tests more sane, by executing each test in a temporary directory by default, rather than running it inside `tests/run-make`. This will have.. a lot of conflicts. Fixes: rust-lang/rust#126080 Closes rust-lang/rust#125726, because it removes `tmp_dir`, lol. r? `@jieyouxu` try-job: x86_64-msvc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-docs
Area: Documentation for any part of the project, including the compiler, standard library, and tools
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-bug
Category: This is a bug.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Most command wrappers assume output artifacts will be emitted to
tmp_dir()
(which calculatesTMPDIR
as is used in tools.mk), which is a scratchpad directory that is intended to be unique for each run-make test so they don't interfere with each other, and that output artifact emission is contained to the directory. Typically command wrappers will have--out-dir=tmp_dir()
presets.The naming of
tmp_dir()
however is pretty bad -- it being a "temporary directory" is not to be confused withenv::temp_dir
.Do note, however, that tools.mk setting
TMPDIR
has other effects:I don't know if this is intentional, but if it is intended to even control where e.g. codegen artifacts are emitted, then setting
TMPDIR
does nothing on Windows: we also need to setTMP
/TEMP
on Windows.The text was updated successfully, but these errors were encountered: