-
Notifications
You must be signed in to change notification settings - Fork 13.3k
create config::tests::detect_src_and_out
test for bootstrap
#109055
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
Signed-off-by: ozkanonur <work@onurozkan.dev>
Have you tested when the |
I did |
Thanks for the PR! |
…bertlarsan68 create `config::tests::detect_src_and_out` test for bootstrap Resolves one of the `FIXME` in bootstrap
This doesn't test everything I would like it to. I was thinking about the following cases when I wrote the comment:
|
@bors r- |
oh ugh it's already in a rollup :( @bors r+ but I would prefer to add more tests, or to add the comment back. |
First 3 works, and I am pretty sure for 4th as well. I haven't check the 5 and 6.
If I force push now, will it take the effect in rollup? |
No. the only way to cancel it is to close the rollup, and this isn't a regression so I don't think that makes sense. |
…iaskrgr Rollup of 9 pull requests Successful merges: - rust-lang#108419 (Stabilize `atomic_as_ptr`) - rust-lang#108507 (use `as_ptr` to determine the address of atomics) - rust-lang#108607 (Don't use fd-lock on Solaris in bootstrap) - rust-lang#108830 (Treat projections with infer as placeholder during fast reject in new solver) - rust-lang#109055 (create `config::tests::detect_src_and_out` test for bootstrap) - rust-lang#109058 (Document BinOp::is_checkable) - rust-lang#109081 (simd-wide-sum test: adapt for LLVM 17 codegen change) - rust-lang#109083 (Update books) - rust-lang#109088 (Gracefully handle `#[target_feature]` on statics) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
I will extend the test around this week |
…t_test, r=jyn514 extend `detect_src_and_out` test > I was thinking about the following cases when I wrote the comment in rust-lang#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 rust-lang#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 rust-lang#109120 partially
…t_test, r=jyn514 extend `detect_src_and_out` test > I was thinking about the following cases when I wrote the comment in rust-lang#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 rust-lang#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 rust-lang#109120 partially
…test, r=jyn514 extend `detect_src_and_out` test > I was thinking about the following cases when I wrote the comment in rust-lang#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 rust-lang#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 rust-lang#109120 partially
Resolves one of the
FIXME
in bootstrap