Skip to content

bug report: rustc panic when run cargo check --all-targets #72910

Closed
@Sherlock-Holo

Description

@Sherlock-Holo

I am using nightly version: rustc 1.45.0-nightly (ad4bc33 2020-06-01)

I tried run cargo check --all-targets with this codes:

#[cfg(test)]
mod tests {
        #[async_std::test]
    async fn identify() {
        const IDENTIFY_BODY: &str = r#"
        {
  "client_id": "test",
  "deflate": false,
  "deflate_level": 6,
  "feature_negotiation": true,
  "heartbeat_interval": 30000,
  "hostname": "test-host",
  "long_id": "test",
  "msg_timeout": 0,
  "output_buffer_size": 16384,
  "output_buffer_timeout": 250,
  "sample_rate": 0,
  "short_id": "test",
  "snappy": false,
  "tls_v1": false,
  "user_agent": "nsq_tail/1.2.0 go-nsq/1.0.7"
}
        "#;

        const IDENTIFY_HEADER: &[u8; 8] = b"IDENTIFY";

        let len = IDENTIFY_BODY.len() as u32;
    }
}

I expected to see this happen: check successfully

Instead, this happened:

error: internal compiler error: src/librustc_middle/ich/impls_ty.rs:94: StableHasher: unexpected region '_#9r

thread 'rustc' panicked at 'Box<Any>', src/librustc_errors/lib.rs:907:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

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

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

note: rustc 1.45.0-nightly (ad4bc3323 2020-06-01) running on x86_64-unknown-linux-gnu

note: compiler flags: -C embed-bitcode=no -C debuginfo=2 -C incremental -C link-arg=-fuse-ld=lld

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

error: aborting due to previous error

error: could not compile `smq`.

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: internal compiler error: src/librustc_middle/ich/impls_ty.rs:94: StableHasher: unexpected region '_#9r

thread 'rustc' panicked at 'Box<Any>', src/librustc_errors/lib.rs:907:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

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

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

note: rustc 1.45.0-nightly (ad4bc3323 2020-06-01) running on x86_64-unknown-linux-gnu

note: compiler flags: -C embed-bitcode=no -C debuginfo=2 -C incremental -C link-arg=-fuse-ld=lld --crate-type lib

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

error: aborting due to previous error

error: build failed

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions