diff options
| author | bors <bors@rust-lang.org> | 2023-04-06 21:18:49 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-04-06 21:18:49 +0000 |
| commit | 28a29282f6dde2e4aba6e1e4cfea5c9430a00217 (patch) | |
| tree | f1f1e43fc8df65cc1901be50ad6325693a892267 /compiler/rustc_macros/src/diagnostics/utils.rs | |
| parent | de74dab880447f5227030b261dbd0f2bc4f32dba (diff) | |
| parent | 925a3040c7f0a84885a91ba8919d1f6d7516302a (diff) | |
| download | rust-28a29282f6dde2e4aba6e1e4cfea5c9430a00217.tar.gz rust-28a29282f6dde2e4aba6e1e4cfea5c9430a00217.zip | |
Auto merge of #109162 - ozkanonur:extend_detect_src_and_out_test, r=jyn514
extend `detect_src_and_out` test > I was thinking about the following cases when I wrote the comment in #109055 > > 1. Running bootstrap from the source root. > 2. Running from a subdirectory of the source root. > 3. Running from outside the source root. > 4. Running on a different machine from where bootstrap was compiled (which will be important > for #107812). You can mostly replicate this by renaming the source root so it no longer exists on disk. > 5. Running with `--build-dir`. > 6. Running with `$RUST_BOOTSTRAP_CONFIG` set in the environment and `build-dir` set in the file. Tested all the topics mentioned above. All worked fine. The test is now also covers if build dir is manually specified in config. r? `@jyn514` helps #109120 partially
Diffstat (limited to 'compiler/rustc_macros/src/diagnostics/utils.rs')
0 files changed, 0 insertions, 0 deletions