-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
reproducing ICE while compiling experimental RSLint on 1.51.0-nightly #81614
Comments
Error: Parsing ping command in comment failed: ...'eanup-crew' | error: expected end of command at >| ' can maybe'... Please let |
Hey Cleanup Crew ICE-breakers! This bug has been identified as a good cc @AminArria @camelid @chrissimpkins @contrun @DutchGhost @elshize @ethanboxx @h-michael @HallerPatrick @hdhoang @hellow554 @henryboisdequin @imtsuki @JamesPatrickGill @kanru @KarlK90 @LeSeulArtichaut @MAdrianMattocks @matheus-consoli @mental32 @nmccarty @Noah-Kennedy @pard68 @PeytonT @pierreN @Redblueflame @RobbieClarken @RobertoSnap @robjtede @SarthakSingh31 @shekohex @sinato @smmalis37 @steffahn @Stupremee @tamuhey @turboladen @woshilapin @yerke |
@rustbot ping icebreakers-cleanup-crew |
Hey Cleanup Crew ICE-breakers! This bug has been identified as a good cc @AminArria @camelid @chrissimpkins @contrun @DutchGhost @elshize @ethanboxx @h-michael @HallerPatrick @hdhoang @hellow554 @henryboisdequin @imtsuki @JamesPatrickGill @kanru @KarlK90 @LeSeulArtichaut @MAdrianMattocks @matheus-consoli @mental32 @nmccarty @Noah-Kennedy @pard68 @PeytonT @pierreN @Redblueflame @RobbieClarken @RobertoSnap @robjtede @SarthakSingh31 @shekohex @sinato @smmalis37 @steffahn @Stupremee @tamuhey @turboladen @woshilapin @yerke |
This was likely caused by #79757. Specifically, this part is where the ICEing code was added. It seems there's a bug in the implementation where it is not always replacing the tabs ahead of time. However, that seems like it should be a |
@camelid Are you saying I can clean up locally and just work around it for now? Or do you potentially still need an |
@camelid Right, perhaps best to change to |
Potentially. Try searching for tabs (literal tabs, not What is an |
@camelid Should I mark the PR as fixing this issue and a new one for working out the root cause, or should this be kept open and reused for the root cause as well? (Unsure if there's a typical workflow for such things here.) |
I'm not sure if there's a usual workflow, but personally I think I would mark it as closing this and then open a new one for working out the underlying cause. Once it no longer panics, this is no longer a severe issue. |
Let's leave the ticket open but remove the ICE tag once that PR is merged. |
This comment has been minimized.
This comment has been minimized.
…tebank Reduce tab formatting assertions to debug only The tab replacement for diagnostics added in rust-lang#79757 included a few assertions to ensure all tab characters are handled appropriately. We've started getting reports of these assertions firing (rust-lang#81614). Since it's only a cosmetic issue, this downgrades the assertions to debug only, so we at least continue compiling even if the diagnostics might be a tad wonky. Minimizes the impact of rust-lang#81614
As discussed, we can remove some of the labels now that the ICE is resolved (but the root cause remains). @rustbot label -I-ICE -I-prioritize +A-diagnostics |
fuzz-rustc found a small example that hits the debug assertion: fn n(){let _:C+d <>
} |
Triage: I don't believe the assertion is being triggered anymore on master (changing the |
I can confirm that the previous comment does no longer trigger an ICE, but I found this case which does trigger it (only with debug assertions enabled): const const |
Code
Trying to compile Kixiron/RSLint@9388cdd, having changed the
Cargo.toml
a the repository root slightly to the following, in preparation for trying some experimental changes to new code that runs a few seconds even with fat LTO:The command line was
nice nice cargo run --locked --release ../../engine262/engine262/src
.Meta
It reproduced after a
cargo clean
. If there are procedures to appropriately handle anrr
trace (it might contain personal/private data by accident, so I'd need some sort of formal agreement to be comfortable sharing it), I'd offer to try to reproduce it underrr
.rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: