Skip to content

E0425 (unresolved name) causes: "error: internal compiler error: encountered incremental compilation error with evaluate_obligation(438f71306b469e95-f644598fa3d5b9b0)" #17883

Open

Description

@epilys

Summary

It seems like a typo (writing PathhBuf instead of PathBuf) triggered an ICE:

error[E0425]: cannot find type `PathhBuf` in this scope
   --> meli/src/contacts/export.rs:254:15
    |
254 |         path: PathhBuf,
    |               ^^^^^^^^ not found in this scope

error: internal compiler error: encountered incremental compilation error with evaluate_obligation(438f71306b469e95-f644598fa3d5b9b0)

I can't provide a minimal verifiable example, so I tagged the before and afters of my WIP code:

The command used was RUST_BACKTRACE=1 cargo clippy --no-deps --all-features --all --tests --examples --benches --bins

Version

rustc 1.99.0 (b940084d7 2026-09-28)
binary: rustc
commit-hash: b940084d7eb6a299eb4bfeb8e34901bc051e7ac4
commit-date: 2026-09-28
host: aarch64-apple-darwin
release: 1.99.0
LLVM version: 23.1.1

Error output

RUST_BACKTRACE=1 cargo clippy --no-deps --all-features --all --tests --examples --benches --bins

Backtrace

$ RUST_BACKTRACE=1 cargo clippy --no-deps --all-features --all --tests --examples --benches --bins
  Checking meli v0.9.0 (_)
error[E0425]: cannot find type `PathhBuf` in this scope
 --> meli/src/contacts/export.rs:254:15
  |
254 |         path: PathhBuf,
  |               ^^^^^^^^ not found in this scope

error: internal compiler error: encountered incremental compilation error with evaluate_obligation(438f71306b469e95-f644598fa3d5b9b0)
|
= note: please follow the instructions below to create a bug report with the provided information
= note: for incremental compilation bugs, having a reproduction is vital
= note: an ideal reproduction consists of the code before and some patch that then triggers the bug when applied and compiled again
= note: as a workaround, you can run `cargo clean -p meli` or `cargo clean` to allow your project to compile


thread 'rustc' (85822018) panicked at /rustc-dev/b940084d7eb6a299eb4bfeb8e34901bc051e7ac4/compiler/rustc_middle/src/verify_ich.rs:82:9:
Found unstable fingerprints for evaluate_obligation(438f71306b469e95-f644598fa3d5b9b0): Ok(EvaluatedToOk)
stack backtrace:
 0: __rustc::rust_begin_unwind
 1: core::panicking::panic_fmt
 2: rustc_middle::verify_ich::incremental_verify_ich_failed
 3: rustc_middle::verify_ich::incremental_verify_ich::<rustc_middle::query::erase::ErasedData<[u8; 2]>>
 4: rustc_query_impl::execution::try_execute_query::<rustc_middle::query::caches::DefaultCache<rustc_type_ir::canonical::CanonicalQueryInput<rustc_middle::ty::context::TyCtxt, rustc_middle::ty::ParamEnvAnd<rustc_middle::ty::predicate::Predicate>>, rustc_middle::query::erase::ErasedData<[u8; 2]>>, true>
 5: <rustc_infer::infer::InferCtxt as rustc_trait_selection::traits::query::evaluate_obligation::InferCtxtExt>::evaluate_obligation
 6: <rustc_infer::infer::InferCtxt as rustc_trait_selection::traits::query::evaluate_obligation::InferCtxtExt>::evaluate_obligation_no_overflow
 7: <rustc_trait_selection::traits::fulfill::FulfillProcessor>::process_trait_obligation
 8: <rustc_trait_selection::traits::fulfill::FulfillProcessor as rustc_data_structures::obligation_forest::ObligationProcessor>::process_obligation
 9: <rustc_data_structures::obligation_forest::ObligationForest<rustc_trait_selection::traits::fulfill::PendingPredicateObligation>>::process_obligations::<rustc_trait_selection::traits::fulfill::FulfillProcessor>
10: <rustc_trait_selection::traits::engine::FulfillmentEngine<rustc_trait_selection::traits::FulfillmentError> as rustc_infer::traits::engine::TraitEngine<rustc_trait_selection::traits::FulfillmentError>>::try_evaluate_obligations
11: rustc_hir_analysis::check::wfcheck::check_impl
12: rustc_hir_analysis::check::check::check_item_type
13: rustc_hir_analysis::check::wfcheck::check_well_formed
    [... omitted 1 frame ...]
14: rustc_hir_analysis::check::wfcheck::check_type_wf
    [... omitted 1 frame ...]
15: rustc_hir_analysis::check_crate
16: rustc_interface::passes::analysis
17: rustc_query_impl::execution::try_execute_query::<rustc_middle::query::caches::SingleCache<rustc_middle::query::erase::ErasedData<[u8; 0]>>, true>
18: rustc_interface::passes::create_and_enter_global_ctxt::<core::option::Option<rustc_interface::queries::Linker>, rustc_driver_impl::run_compiler::{closure#0}::{closure#1}>
19: rustc_interface::interface::run_compiler::<(), rustc_driver_impl::run_compiler::{closure#0}>::{closure#2}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

error: the compiler unexpectedly panicked. This is a bug

note: we would appreciate a bug report: https://github.com/rust-lang/rust-clippy/issues/new?template=ice.yml

note: rustc 1.99.0 (b940084d7 2026-09-28) running on aarch64-apple-darwin

note: compiler flags: --crate-type lib -C embed-bitcode=no -C debuginfo=2 -C split-debuginfo=unpacked -C incremental=[REDACTED]

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

query stack during panic:
#0 [evaluate_obligation] evaluating trait selection obligation `core::option::Option<alloc::boxed::Box<melib::error::Error>>: core::marker::Sync`
#1 [check_well_formed] checking that `contacts::export::<impl at meli/src/contacts/export.rs:309:1: 309:39>` is well-formed
#2 [check_type_wf] checking that types are well-formed
#3 [analysis] running analysis passes on crate `meli`
end of query stack
note: Clippy version: clippy 0.1.99 (b940084d7e 2026-09-28)

For more information about this error, try `rustc --explain E0425`.
error: could not compile `meli` (lib) due to 2 previous errors
warning: build failed, waiting for other jobs to finish...
error: could not compile `meli` (lib test) due to 1 previous error


Activity

  1. added
    C-bugCategory: Clippy is not doing the correct thing
    I-ICEIssue: Clippy panicked, giving an Internal Compilation Error (ICE) ❄️
    on Oct 15, 2026
  2. epilys commented on Oct 15, 2026

    @epilys
    Author

    It seems that this also gets triggered without clippy, so I will file a bug in https://github.com/rust-lang/rust as well.

    EDIT: rust-lang/rust#164347

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-bugCategory: Clippy is not doing the correct thingI-ICEIssue: Clippy panicked, giving an Internal Compilation Error (ICE) ❄️

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions