-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
thread 'main' panicked at 'assertion failed: !require_bitcode', src/tools/cargo/src/cargo/core/compiler/lto.rs:49:9 #8223
Comments
The assertion was added in #8192 |
Cargo no longer panics if I remove the |
I cannot reproduce this on my end. |
Did you make sure that you are on latest nightly ( |
ah yes, |
Thanks for the bug report and reproduction steps! This shoudl be fixed in #8226. |
Update assertions in LTO calculations Turns out a case I thought didn't happen can indeed happen. Units may depend on other units which are LTO-able because integration tests can depend on binaries. Handle that case internally and remove a few panics. Closes #8223
…mulacrum submodules: update cargo from f534844c2 to cb06cb269 Changes: ```` more clippy fixes Document that bench is unstable in the man page. Update assertions in LTO calculations Updated comments in resolve.rs to reflect actual data strcture used. Try to remove secrets from http.debug. Revert always computing filename Metadata. clean -p: call `get_many` once. Implement new `clean -p` using globs. Rework how Cargo computes the rustc file outputs. Add CrateType to replace LibKind. ```` I'd like to get the fix for rust-lang/cargo#8223 into nightly asap. r? @ehuss
Problem
Cargo crashed while running
cargo test --verbose --release --all -- --nocapture
Steps
Possible Solution(s)
Notes
Output of
cargo version
:cargo 1.45.0-nightly (f534844c2 2020-05-06)
The text was updated successfully, but these errors were encountered: