-
Notifications
You must be signed in to change notification settings - Fork 13.4k
ICE in 1.49.0 nightly 2020-11-01 on windows #78660
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
Comments
I think #75534 is the cause, cc @Aaron1011. Backtrace
|
MCVE: run // bug.rs
fn main() {
["hi"].into_iter();
} |
Assigning |
I got the same error on Linux while compiling lazy_static. https://cirrus-ci.com/task/6280736288276480 . |
This will be fixed by #78663 |
Temporarily downgrade rustc nightly during CI minver to workaround a Rustc bug. rust-lang/rust#78660
Temporarily downgrade rustc nightly during CI minver to workaround a Rustc bug. rust-lang/rust#78660
Temporarily downgrade rustc nightly during CI minver to workaround a Rustc bug. rust-lang/rust#78660
…tmandry Fix ICE when a future-incompat-report has its command-line level capped Fixes rust-lang#78660 With PR rust-lang#75534 merged, we now run more lint-related code for future-incompat-report, even when their final level is Allow. Some lint-related code was not expecting `Level::Allow`, and had an explicit panic. This PR explicitly tracks the lint level set on the command line before `--cap-lints` is applied. This is used to emit a more precise error note (e.g. we don't say that `-W lint-name` was specified on the command line just because a lint was capped to Warn). As a result, we can now correctly emit a note that `-A` was used if we got `Level::Allow` from the command line (before the cap is applied).
Now that rust-lang/rust#78660 is fixed
Code
Simply building the rusty-xinput crate in the dependency chain seems to have triggered it. See https://github.com/bevyengine/bevy/pull/769/checks?check_run_id=1340257075
Meta
Rust version from the build
Error output
Backtrace
I'm sorry - I don't have access to a windows environment to reproduce this!
The text was updated successfully, but these errors were encountered: