`./x.py test --bless tests/mir-opt/` fails with `no entry found for key`
Open
Nobody has claimed this yet.
A-cross
A-sanitizers
C-bug
T-bootstrap
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
$ ./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
0d11be5aabe0cd49609fff5fce57c4691a22fe55
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at src/bootstrap/src/core/build_steps/test.rs:2039 and reproduce with ./x.py test --bless tests/mir-opt/ using build.sanitizers = true. Compare the failure with target.i686-pc-windows-msvc.sanitizers = false to understand the affected configuration path. Done means the command no longer panics with "no entry found for key" under the reported configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100