This repository has been archived by the owner on Dec 26, 2019. It is now read-only.
libigl: Exclude broken toolchains #374
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I have checked that this pull request contains only
.travis.yml/appveyor.ymlchanges or commits merged from thepkg.templatebranch. All other changes sendto https://github.com/ruslo/hunter. Yes
I have checked that no toolchains removed from CI configs, they are commented
out instead so other developers can enable them back easily and to simplify
merge conflict resolution. Yes
I have checked that for every commented out toolchain there is a link to the
broken CI build page or to the minimum compiler requirements documentation
so other developers can figure out what was the problem exactly. Yes
I have checked that for every enabled toolchain corresponding package passed
all stages of update cycle: test/merge/upload/release. Yes
@ruslo