-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Allow using download-ci-llvm = true
outside the git checkout
#98526
Conversation
|
3ce8ed5
to
071dd98
Compare
Can you look through the other git invocations in bootstrap to check those for similar problems? I think download-rustc's invocation here has the same problem, at least, and there's maybe a few more -- it'd be great to solve all of them rather than just one case. I'm not sure the submodule checkouts work properly either. |
071dd98
to
0e58792
Compare
Good catch, thanks. Fixed that and a bunch of ohter issues. I haven't run a full build with these changes, but
they do :)
|
I'm not too worried about us validating it, but it seems like moving one of the CI builders to a non-in-tree directory might be a good way to test this without all that much hassle, in theory. It's probably a good bit of work to convince CI to behave if we do that though, so maybe not the best use of time for such a niche feature; I'm happy with x.py check as testing for now. |
r=me if you don't want to spend the cycles adding that builder here. |
Yeah, I think I'd prefer to avoid spending time on this until / unless someone complains. @bors r=Mark-Simulacrum rollup |
📌 Commit 0e58792 has been approved by |
…ut, r=Mark-Simulacrum Allow using `download-ci-llvm = true` outside the git checkout `@bjorn3` noticed that this is already allowed today when download-llvm is disabled, but breaks with it enabled: ``` $ ./rust2/x.py build fatal: not a git repository (or any of the parent directories): .git thread 'main' panicked at 'command did not execute successfully: "git" "rev-list" "--author=bors@rust-lang.org" "-n1" "--first-parent" "HEAD" "--" "/home/jnelson/rust-lang/rust2/src/llvm-project" "/home/jnelson/rust-lang/rust2/src/bootstrap/download-ci-llvm-stamp" "/home/jnelson/rust-lang/rust2/src/version" expected success, got: exit status: 128', src/bootstrap/native.rs:134:20 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` Support it too for consistency. It's unclear to me when anyone would need to use this, but `@bjorn3` feels we should support it, and it's not much additional effort to get it working.
…ut, r=Mark-Simulacrum Allow using `download-ci-llvm = true` outside the git checkout ``@bjorn3`` noticed that this is already allowed today when download-llvm is disabled, but breaks with it enabled: ``` $ ./rust2/x.py build fatal: not a git repository (or any of the parent directories): .git thread 'main' panicked at 'command did not execute successfully: "git" "rev-list" "--author=bors@rust-lang.org" "-n1" "--first-parent" "HEAD" "--" "/home/jnelson/rust-lang/rust2/src/llvm-project" "/home/jnelson/rust-lang/rust2/src/bootstrap/download-ci-llvm-stamp" "/home/jnelson/rust-lang/rust2/src/version" expected success, got: exit status: 128', src/bootstrap/native.rs:134:20 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` Support it too for consistency. It's unclear to me when anyone would need to use this, but ``@bjorn3`` feels we should support it, and it's not much additional effort to get it working.
…ut, r=Mark-Simulacrum Allow using `download-ci-llvm = true` outside the git checkout ```@bjorn3``` noticed that this is already allowed today when download-llvm is disabled, but breaks with it enabled: ``` $ ./rust2/x.py build fatal: not a git repository (or any of the parent directories): .git thread 'main' panicked at 'command did not execute successfully: "git" "rev-list" "--author=bors@rust-lang.org" "-n1" "--first-parent" "HEAD" "--" "/home/jnelson/rust-lang/rust2/src/llvm-project" "/home/jnelson/rust-lang/rust2/src/bootstrap/download-ci-llvm-stamp" "/home/jnelson/rust-lang/rust2/src/version" expected success, got: exit status: 128', src/bootstrap/native.rs:134:20 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` Support it too for consistency. It's unclear to me when anyone would need to use this, but ```@bjorn3``` feels we should support it, and it's not much additional effort to get it working.
@bjorn3 noticed that this is already allowed today when download-llvm is disabled, but breaks with it enabled: ``` $ ./rust2/x.py build fatal: not a git repository (or any of the parent directories): .git thread 'main' panicked at 'command did not execute successfully: "git" "rev-list" "--author=bors@rust-lang.org" "-n1" "--first-parent" "HEAD" "--" "/home/jnelson/rust-lang/rust2/src/llvm-project" "/home/jnelson/rust-lang/rust2/src/bootstrap/download-ci-llvm-stamp" "/home/jnelson/rust-lang/rust2/src/version" expected success, got: exit status: 128', src/bootstrap/native.rs:134:20 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` Support it too for consistency. It's unclear to me when anyone would need to use this, but @bjorn3 feels we should support it, and it's not much additional effort to get it working. This also updates a bunch of other git commands that were similarly depending on the current directory.
0e58792
to
56e42b8
Compare
I've discarded all the toolstate changes. It's extremely rare to run toolstate outside of CI, and also extremely rare to run x.py from outside the checkout; I don't think we need to support both at once. @bors r=Mark-Simulacrum rollup=iffy |
☀️ Test successful - checks-actions |
Finished benchmarking commit (adaddb5): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
@bjorn3 noticed that this is already allowed today when download-llvm is disabled, but breaks with it enabled:
Support it too for consistency. It's unclear to me when anyone would need to use this, but @bjorn3
feels we should support it, and it's not much additional effort to get it working.