-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
x.py test --bless tidy step does not work outside of root dir #122202
Labels
C-bug
Category: This is a bug.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Comments
rustbot
added
the
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
label
Mar 8, 2024
jieyouxu
added
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
and removed
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
labels
Mar 8, 2024
x.py in general assumes you are in the root. It's not just tidy. E.g. building from a subdir will not use the existing build artifacts in /build |
Not really. Many people work from outside the root (including me). Path for the build directory is entirely different story and can be configured. |
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Mar 9, 2024
Rollup merge of rust-lang#122209 - onur-ozkan:fix-tidy-path-resolution, r=compiler-errors fix incorrect path resolution in tidy Previously, reading the current path from the environment led to failure when invoking x from outside the source root. This change fixes this issue by passing the already resolved root path into `ui_tests::check`. Fixes rust-lang#122202
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-bug
Category: This is a bug.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
I tried this: In a subdirectory
root/objdir/
, after a successful build, I then did../x.py test --stage 1 --bless
I expected to see this happen: The test files that need updating get updated.
Instead, this happened: tidy panicked
I believe this is because of this code, which seems to contain an assumption that the current_dir will be the root of the source tree, which is not true in general for
x.py
:rust/src/tools/tidy/src/ui_tests.rs
Line 187 in 74acabe
The text was updated successfully, but these errors were encountered: