-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
ICE: "no errors encountered even though delay_span_bug
issued" on tantivy v0.21 in release mode
#116333
Labels
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
P-high
High priority
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
aumetra
added
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
labels
Oct 2, 2023
rustbot
added
the
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
label
Oct 2, 2023
aumetra
changed the title
ICE: no errors encountered even though
ICE: "no errors encountered even though Oct 2, 2023
delay_span_bug
issued on tantivy v0.21 in release modedelay_span_bug
issued" on tantivy v0.21 in release mode
rustbot
added
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
I-prioritize
Issue: Indicates that prioritization has been requested for this issue.
labels
Oct 2, 2023
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-high |
rustbot
added
P-high
High priority
and removed
I-prioritize
Issue: Indicates that prioritization has been requested for this issue.
labels
Oct 2, 2023
fmease
removed
the
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
label
Oct 2, 2023
Minimized to: fn checkpoints() -> impl Iterator {
Some(()).iter().flat_map(|_| std::iter::once(()))
}
fn block_checkpoints() -> impl Iterator {
checkpoints()
}
fn iter_raw() -> impl Iterator {
let mut iter = block_checkpoints();
(0..9).map(move |_| {
iter.next();
})
} |
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Oct 5, 2023
Move subtyper below reveal_all and change reveal_all In previous attempt rust-lang#116378 we tried to handle `Opaque` in few different places, but this isn't necessary, after moving subtyper below reveal_all and calling `super_place` on reveal_all, issues cease to exist. r? `@oli-obk` Fixes rust-lang#116332 Fixes rust-lang#116265 Fixes rust-lang#116383 Fixes rust-lang#116333
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 5, 2023
Rollup merge of rust-lang#116415 - ouz-a:move_subtyper, r=oli-obk Move subtyper below reveal_all and change reveal_all In previous attempt rust-lang#116378 we tried to handle `Opaque` in few different places, but this isn't necessary, after moving subtyper below reveal_all and calling `super_place` on reveal_all, issues cease to exist. r? ``@oli-obk`` Fixes rust-lang#116332 Fixes rust-lang#116265 Fixes rust-lang#116383 Fixes rust-lang#116333
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
P-high
High priority
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Code
The issue occurred when compiling
tantivy
in release mode.I'm not sure how the create a good min repr for such a rather complex codebase, but the same error occurs when compiling one of their basic examples in release mode.
https://github.com/quickwit-oss/tantivy/blob/0.21/examples/basic_search.rs
Meta
rustc --version --verbose
:Error output
rustc ICE output
Backtrace
The text was updated successfully, but these errors were encountered: