-
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
Coverage on stable 1.79.0 fails with : maybe try to call try_normalize_erasing_regions
instead
#125353
Comments
Ok, I have some bad and some good news. The bad one is that this bug is landed in stable 1.79.0 😢 The good one is that I can give you a repo to reproduce it: Clone https://github.com/HorizenLabs/zkVerify , here the follow command reproduce the issue: cargo llvm-cov --all-features --workspace --lcov --output-path lcov.info That's a regression on stable from 1.78 to 1.79 I'm sorry, I know that's a huge but I don't know how to narrow it. |
try_normalize_erasing_regions
instead try_normalize_erasing_regions
instead
@jieyouxu Now that this bug is landed on stable shall not be better to take another look on it? If there's something that I can do let me know. |
I've run into this issue too, exactly the same setup (substrate project, build and test works fine, but coverage build fails with this error) |
cc @Zalathar maybe you have any ideas on how to make the example smaller? |
Does the same issue occur when you do a non-coverage build with Coverage enables that as a side-effect, so this might be a symbol-mangling issue rather than a coverage issue (e.g. see also #116303). |
Yes! If I run with |
I can confirm it too: RUSTFLAGS="-Csymbol-mangling-version=v0" cargo build --release meet the same issue. |
If this is reproducible with |
Facing the same issue here, in |
Could it be #127351 ? - appeared around the same time. |
Code
Unfortunately I cannot provide a minimal example. I meet this issue while I'm trying to run coverage on nightly to experiment on
coverage_attribute
feature on an substrate based project.I've experimented this issue with both
nightly-2024-05-20
andnightly-2024-04-
0`. I cannot bisect on it because the compilation time is too hugeThe good news is that botn
cargo +nightly build
cargo +nightly test
work fine and the issue seams just related to the coverage stuff.Meta
rustc --version --verbose
:Error output
rustc-ice-2024-05-21T08_17_56-165861.txt
Backtrace
The text was updated successfully, but these errors were encountered: