Re-format skip sections - #651
Merged
Merged
Conversation
Member
|
Or should this be merged first? |
Contributor
Author
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
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.
Per http://conda.pydata.org/docs/building/meta-yaml.html#skipping-builds I've put all the skips as comments.
I've put them on one line, so you can grep for "skip: " and get a quick summary of what's not getting built.
If there's a comment explaining the skip, put it on one line before (so you can
grep -B1).We should make people explain their skips. There are a lot of skipped configurations whose reasoning is not obvious at all. This is important if someone wants to fix it