[compiletest
-related cleanups 4/7] Make the distinction between root build directory vs test suite specific build directory in compiletest less confusing
#136542
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Caution
This PR is stacked on top of #136441, #136472 and #136474. This PR contains their commits, the prerequisite PRs must be merged first, then this PR will need to be rebased.
Reference for overall changes: #136437
Part 4 of 7 of the
compiletest
-related cleanups PR series.Summary
--build-base
compiletest flag, and introduce--build-{root,test-suite-root}
flags instead.--build-base
previously actually is test suite specific build directory, not the rootbuild/
directory.--build-root
instead of doing multiple layers of parent unwrapping1 based on the test suite specific build directory.to_path_buf()
.r? bootstrap
Footnotes
Please do not unwrap the parents. ↩