-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Some bootstrap tests fail with custom rustc #105766
Labels
C-bug
Category: This is a bug.
regression-from-stable-to-stable
Performance or correctness regression from one stable version to another.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
Comments
@rustbot claim |
FYI we had the same problem on Debian, worked around with a custom patch: https://salsa.debian.org/rust-team/rust/-/merge_requests/24/diffs?commit_id=f249e1b3f6a71bdf040e98214ea360f4955b0a09 |
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jul 8, 2024
…stc, r=<try> Fix running bootstrap tests with a local Rust toolchain as the stage0 When configuring a local Rust toolchain as the stage0 (with `build.rustc` and `build.cargo` in `config.toml`) we noticed there were test failures (both on the Python and the Rust side) due to bootstrap not being able to find rustc and Cargo. This was due to those two `config.toml` settings not being propagated in the tests. This PR fixes the issue by ensuring rustc and cargo are always configured in tests, using the parent bootstrap's `initial_rustc` and `initial_cargo`. try-job: x86_64-msvc Fixes rust-lang#105766
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jul 10, 2024
Rollup merge of rust-lang#126476 - ferrocene:pa-bootstrap-test-local-rustc, r=onur-ozkan Fix running bootstrap tests with a local Rust toolchain as the stage0 When configuring a local Rust toolchain as the stage0 (with `build.rustc` and `build.cargo` in `config.toml`) we noticed there were test failures (both on the Python and the Rust side) due to bootstrap not being able to find rustc and Cargo. This was due to those two `config.toml` settings not being propagated in the tests. This PR fixes the issue by ensuring rustc and cargo are always configured in tests, using the parent bootstrap's `initial_rustc` and `initial_cargo`. try-job: x86_64-msvc Fixes rust-lang#105766
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
C-bug
Category: This is a bug.
regression-from-stable-to-stable
Performance or correctness regression from one stable version to another.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
Command
I tried this with Rust 1.66.0, simplified from my build for Fedora:
$ ./configure --local-rust-root=/usr $ ./x test bootstrap
I expected to see this happen: passing tests
Instead, this happened: 20
builder::tests::...
failures, all of this sort:My stage0 should be using
/usr/bin/rustc
.Version it worked on
It most recently worked on: Rust 1.65.0
Version with regression
rustc-1.66.0-src/version
:I bisected this to #98483, commit 55c040e, which stopped using
CARGO
andRUSTC
environment variables when building aConfig
.Backtrace
Backtrace
@rustbot modify labels: +regression-from-stable-to-stable -regression-untriaged +A-bootstrap
The text was updated successfully, but these errors were encountered: