-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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 compiler/rustc_abi
no longer works
#129727
Labels
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
Aug 29, 2024
jieyouxu
added
the
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
label
Aug 29, 2024
onur-ozkan
removed
the
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
label
Aug 29, 2024
@rustbot claim |
This was referenced Aug 30, 2024
workingjubilee
added a commit
to workingjubilee/rustc
that referenced
this issue
Sep 6, 2024
… r=albertlarsan68 Make `./x.py <cmd> compiler/<crate>` aware of the crate's features Does not fix rust-lang#129727 on its own as the way the parallel-compiler cfg and feature flags are setup being generally incompatible with `resolver = 2` but it progresses on the issue. But this should in theory allow compiler crates to work that do not depend on the parallel compiler stuff (so some leaf crates).
workingjubilee
added a commit
to workingjubilee/rustc
that referenced
this issue
Sep 6, 2024
… r=albertlarsan68 Make `./x.py <cmd> compiler/<crate>` aware of the crate's features Does not fix rust-lang#129727 on its own as the way the parallel-compiler cfg and feature flags are setup being generally incompatible with `resolver = 2` but it progresses on the issue. But this should in theory allow compiler crates to work that do not depend on the parallel compiler stuff (so some leaf crates).
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Sep 6, 2024
Rollup merge of rust-lang#129781 - Veykril:lw-x-py-compiler-features, r=albertlarsan68 Make `./x.py <cmd> compiler/<crate>` aware of the crate's features Does not fix rust-lang#129727 on its own as the way the parallel-compiler cfg and feature flags are setup being generally incompatible with `resolver = 2` but it progresses on the issue. But this should in theory allow compiler crates to work that do not depend on the parallel compiler stuff (so some leaf crates).
Whoops, I did not mean to close this with that PR (and I can't reopen it for some reason) this is still an issue |
#131093 may be a duplicate of this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This regressed with #128722
Running
./x.py test compiler/rustc_abi
(as well as for most other compiler crates) no longer works, resulting in an error similar to the following:The text was updated successfully, but these errors were encountered: