Revert "[ci] Separately track MSRV and MWRV" #811
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reverts #810
It turns out that while #810 was itself fine, building on it is currently impossible. In particular, when we lower the MWRV to lower than the MSRV, Cargo invocations in CI complain because we're asking it to compile using a toolchain lower than the documented MSRV. This can be bypassed using
--ignore-rust-version. However, there's no way to instruct thetrybuildcrate (which runs our UI tests) to pass that flag when it invokes Cargo, and so the UI tests fail without recourse.