Merged
Conversation
Member
|
Looking at the CPU and memory graphs on the results, it looks like we rarely go above 2 cpus and only use a tiny amount of the available memory. Given that, it might be a good idea to use: I don't think it will change the run time too much, but it might ensure our jobs get scheduled faster at times of high demand. |
Contributor
Author
|
Agreed. I've already tweaked the Samtools version to do this and plan to go back and modify the htslib one. I don't see how to tweak these for the Mac instances though. It may not be possible there. |
Contributor
Author
|
A few minor tweaks squashed into one commit
|
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.
This is a replacement for Travis, but it doesn't remove it (yet) so we can compare side by side for a while. Compared to Travis is lacks the s390x test.
However we have gcc:latest (Debian), clang (via ubuntu:devel) and MacOS X (clang only). The mix of maintainer-checks, with/without config, libdeflate, pedantic and address sanitizer are sprinkled across the various environments so we don't have a huge matrix. We also test libdeflate integration from local source (Debian, MacOS) and from OS installed package (Ubuntu).
Everything launches in parallel bar the 2nd MacOS X instance as it appears we're limited to just 1.
Other possibilities could include pretty much anything on docker-hub, so we could consider 32-bit builds if we feel it's worth it.
That also means we have the potential for custom containers with the prerequisites already installed so we have a leaner instance startup. The ubuntu ones spend maybe 25-30% of their time installing compilers and libraries.
Example builds can be seen here:
https://cirrus-ci.com/build/5071567057059840