Open
Conversation
The Travis build uses gcc-v5 and cmake v3.2. The build succeeds if test_SatsumaSynteny2 exits successfully. The output redirected to /dev/null; this is required since Travis does not like long messages (failing the build if log is greater than 4MB). NOTE: I had to decrement the required cmake version from 3.3 to 3.2 in order to be compatible with Travis.
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
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.
These are all pretty minor changes.
I added a gitignore file so the temporary files won't clutter the repository, are easily removed, and won't accidentally committed.
I standardized formatting in the README. Replaced carriage returns with newlines and things like that. Also I wrapped all the lines at 80 characters; this has no impact on the compiled HTML, but makes reading easier for people in text editors. I can revert this if you like.
The biggest change is that addition of continuous integration with Travis. Most major repositories on github now use Travis (or a similar service) to tell users whether a given commit/version builds successfully and passes whatever tests the developers subject the code to. If you jump over to my fork, you'll see a little green shield above the README that says "build passing". You can adapt the .travis.yml file to run whatever tests you like.
You will need to update the first line in the README to point to your repository. Just replace the line with this:
[](https://travis-ci.org/bioinfologics/satsuma2)