Build libyaml on travis#195
Closed
perlpunk wants to merge 4 commits into
Closed
Conversation
perlpunk
force-pushed
the
travis-install-libyaml
branch
from
174a2f8 to
22604bf
Compare
Member
|
Applied. Pushed. Thanks! |
This was referenced Mar 9, 2021
This was referenced Mar 17, 2021
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.
See also #60 and #184
We fetch the latest libyaml release and build it, so the tests
run both pure python and libyaml tests.
Tests are currently failing and should pass again when applying
yaml/libyaml#122
(and adjusting the libyaml tag we are checking out in .travis.yml)