Let LLVM 12 roll in #11637
Merged
Let LLVM 12 roll in #11637
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
sbc100
approved these changes
Jul 15, 2020
sbc100
added a commit
that referenced
this pull request
Jan 28, 2021
This change temporarily disables the version check to allow the llvm change to roll in. Copied from the previous time around: #11637.
sbc100
added a commit
that referenced
this pull request
Jan 28, 2021
This change temporarily disables the version check to allow the llvm change to roll in. Copied from the previous time around: #11637.
sbc100
added a commit
that referenced
this pull request
Jan 28, 2021
This change temporarily disables the version check to allow the llvm change to roll in. Copied from the previous time around: #11637.
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.
Looks like LLVM 12 was just bumped as the new version number,
https://logs.chromium.org/logs/emscripten-releases/buildbucket/cr-buildbucket.appspot.com/8874713585966760400/+/steps/Emscripten_testsuite__upstream__other_/0/stdout
Is there a better way to do this than disabling the test and the check manually?