diff options
| author | bors <bors@rust-lang.org> | 2025-07-05 12:42:59 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2025-07-05 12:42:59 +0000 |
| commit | 6dec76f1c2809fded082dd44d3752d3f6220d767 (patch) | |
| tree | f033f0b9d8a6a94425c5d86a532c3503ff8f70fa /compiler/rustc_pattern_analysis/tests/complexity.rs | |
| parent | fd9ca711a3a0e2bd5bd33a345fa4439348111006 (diff) | |
| parent | 006e97a234baf050e599576a7bce239173ce5556 (diff) | |
| download | rust-6dec76f1c2809fded082dd44d3752d3f6220d767.tar.gz rust-6dec76f1c2809fded082dd44d3752d3f6220d767.zip | |
Auto merge of #143474 - jieyouxu:bootstrap-llvm-snapshot, r=Kobzol
Pretend in bootstrap snapshot tests that we always build in-tree LLVM Otherwise, depending on whether CI LLVM is inhibited or if an externally-provided LLVM is used, bootstrap host LLVM build step could be missing in step snapshots. Note that I'm not sure if this is the *right* solution (this might be *a* solution). I imagine we do want to control for the set of configuration that these snapshot tests are run, as much as possible. r? `@Kobzol`
Diffstat (limited to 'compiler/rustc_pattern_analysis/tests/complexity.rs')
0 files changed, 0 insertions, 0 deletions