`./x.py test --bless tests/mir-opt/` fails with `no entry found for key`

[tmiasko]

$ ./x.py test --bless tests/mir-opt/
..

Building stage1 library artifacts (x86_64-unknown-linux-gnu -> i686-pc-windows-msvc)
    Finished `release` profile [optimized] target(s) in 0.04s

thread 'main' panicked at src/bootstrap/src/core/build_steps/test.rs:2039:47:
no entry found for key

Bootstrap configuration (bootstrap.toml)

build.sanitizers = true

It is possible to work around the issue with following bootstrap configuration:

build.sanitizers = true
target.i686-pc-windows-msvc.sanitizers = false

HEAD

0d11be5

[jieyouxu]

Can you please share your build config? Against 0d11be5 I can't repro this failure with build.sanitizers = true, though there are some very questionable warnings:

warning: dropping unsupported crate type `dylib` for target `i686-unknown-linux-musl-synthetic-miropt-abort-5915297940249345829`

warning: `std` (lib) generated 1 warning
    Checking rustc-std-workspace-std v1.99.0 (/home/joe/repos/rust/library/rustc-std-workspace-std)
    Checking unicode-width v0.2.1
    Checking rustc-literal-escaper v0.0.4
    Checking proc_macro v0.0.0 (/home/joe/repos/rust/library/proc_macro)
    Checking getopts v0.2.23
    Checking test v0.0.0 (/home/joe/repos/rust/library/test)
    Checking sysroot v0.0.0 (/home/joe/repos/rust/library/sysroot)
    Finished `release` profile [optimized + debuginfo] target(s) in 26.24s
Testing stage1 compiletest suite=mir-opt mode=mir-opt (x86_64-unknown-linux-gnu -> i686-unknown-linux-musl-synthetic-miropt-abort(/home/joe/repos/rust/build/synthetic-target-specs/i686-unknown-linux-musl-synthetic-miropt-abort.json))

[jieyouxu]

Nevermind, I see: I can repro without an explicit --target.

[jieyouxu]

Looks like it's failing on

            // Add the address sanitizer runtime to the PATH - it is located next to cl.exe.
            let asan_runtime_path = builder.cc[&target].path().parent().unwrap().to_path_buf();

on a linux host

[jieyouxu]

Hm, cc @rcvalle re. #123617, is it even possible to cross-compile to target {i686,x86_64}-pc-windows-msvc with sanitizers enabled? Cuz we don't and can't ship the Microsoft-provided ASAN runtimes on a e.g. a linux host right?

    pub fn needs_sanitizer_runtime_built(&self, target: TargetSelection) -> bool {
        // MSVC uses the Microsoft-provided sanitizer runtime, but all other runtimes we build.
        !target.is_msvc() && self.sanitizers_enabled(target)
    }