test: allow bootstrap tests to succeed when targeted toolchains already exist #695
Conversation
This file contains hidden or 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
Collaborator
|
Thanks! Rebasing your branch to |
maxwell3025
force-pushed
the
test-suite-elan-fix
branch
from
4b6c7f5 to
1db908f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, running tests locally as described in
dev.mdworks at most one time.In subsequent runs, the user's local
elaninstallation already has the test and build toolchains installed.This causes
elan toolchain install leanprover/lean4:x-y-zto fail with the messageThis PR makes the assertion succeed if the
...is already installederror is printed, even if the exit code indicates failure.This allows the test suit to be run multiple times locally.