Skip to content

"failed to process buffered lint here" with macro call in async block #81724

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

Closed
clehner opened this issue Feb 3, 2021 · 2 comments
Closed

"failed to process buffered lint here" with macro call in async block #81724

clehner opened this issue Feb 3, 2021 · 2 comments
Labels
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.

Comments

@clehner
Copy link
Contributor

clehner commented Feb 3, 2021

This error started appearing with nightly a few days ago.

The source code triggering it is here: https://github.com/timothee-haudebourg/json-ld/blob/9b0e4521f0f600304c508be17021986f90fe07ba/src/expansion/element.rs#L223

This happens when running e.g. cargo build or cargo test.

I was able to minimize the code triggering the error to the following, in the json-ld crate:

diff --git a/src/lib.rs b/src/lib.rs
index e84e86e..c216df1 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -52,0 +53,4 @@ pub use context::{
+
+async fn foo() {
+    warn!("foo {}", "bar")
+}

But I have not been able to reproduce it in a clean new crate.

This warn macro is from the log crate. The error doesn't happen if a semicolon is used after the macro call.

The original error:

error: internal compiler error: failed to process buffered lint here
   --> src/expansion/element.rs:223:8
    |
223 | ...                   warn!("failed to expand key `{}`", key)
    |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: delayed at /rustc/04caa632dd10c2bf64b69524c7f9c4c30a436877/compiler/rustc_lint/src/early.rs:384:18
    = note: this error: internal compiler error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

thread 'rustc' panicked at 'no errors encountered even though `delay_span_bug` issued', compiler/rustc_errors/src/lib.rs:974:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md

note: rustc 1.51.0-nightly (04caa632d 2021-01-30) running on x86_64-unknown-linux-gnu

note: compiler flags: -C embed-bitcode=no -C debuginfo=2 -C incremental --crate-type lib

note: some of the compiler flags provided by cargo are hidden

query stack during panic:
end of query stack
error: could not compile `json-ld`

To learn more, run the command again with --verbose.

@clehner clehner 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 Feb 3, 2021
@jonas-schievink
Copy link
Contributor

duplicate of #81531

@clehner
Copy link
Contributor Author

clehner commented Feb 3, 2021

Thanks @jonas-schievink, sorry for the dupe

timothee-haudebourg added a commit to timothee-haudebourg/json-ld that referenced this issue Feb 5, 2021
Add semicolon after warn

Work around error appearing in Rust nightly 2021-01-30 (rust-lang/rust#81531, rust-lang/rust#81724)
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) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

2 participants