Make bors check compiletest
builds from both stage0 and stage1 rustc
#18012
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.
Make bors check
compiletest
builds from both stage0 and stage1 rustcTo reproduce issue on commit ba24610
it does not suffice to add just
check-build-compiletest
tocheck-secondary
; one must also ensure thatcheck-build-compiletest
precedes the satisification of the
check
rule.Otherwise hidden dependencies of
compiletest
would end up gettingsatisfied when make builds
rustc
at each stage in order toeventually run
check-stage2
.So to handle that I moved
check-secondary
beforecheck
in thecheck-all
rule that bors uses, and for good measure, I also putcheck-build-compiltest
at the front of thecheck-secondary
rule'sdependencies.
My understanding is that running
check-secondary
should berelatively cheap, and thus such a reordering will not hurt bors.
Fix #17883.