Tweaks to test-build.sh #51
Merged
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
Fix links to mailing list archives Fix location of issue tracking
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This makes test-build.sh actually run for me, and adds some documentation so that people who are not already familiar with the infrastructure-pelican tools will know how and where to do the necessary stuff. Note that while the script ends with
ERROR Cannot load plugin
gfm_utils.py:117libcmark-gfm.dylib not found. See build-cmark.sh. Error:
The script does in fact run to completion and build the test site. Could use some tips in how to get rid of that error message, but it seems unnecessary.