Updated custom_paths for picard-1.124 and above#796
Updated custom_paths for picard-1.124 and above#796boegel merged 7 commits intoeasybuilders:developfrom
Conversation
|
Automatic reply from Jenkins: Can I test this? |
There was a problem hiding this comment.
rather than copy-pasting this whole block, it would be better to change the logic that defines the jar_files list?
How familiar are you with Python @nathanhaigh? Let us know if you're up for this.
There was a problem hiding this comment.
I'm not familiar with Python - I'm a Perl guy! :)
I'll have a bash at it though!
|
Jenkins: ok to test |
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1556/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1578/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
@boegel This now implements a comprehensive |
There was a problem hiding this comment.
hmm, do we want this one per line? I'd collapse this by listing multiple items on a single line, but keeping it down to max 120 chars line length?
|
Looks good, but let's make this less verbose/long (vertically)? |
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1690/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
Do you really want multiple elements in |
|
@nathanhaigh: well, it's a matter of preference, sure... There's no other easyblock I know of that has a list this long with one entry per line. I agree it makes things more readable, but how often is that really relevant in this case? Anyway, it's up to you in this case, I don't feel strongly enough about it to make this a blocker. |
|
Ok, I'll leave it as it is :) I'm finished with this PR, so please merge when you're happy. |
| jar_files = ['picard'] | ||
| if LooseVersion(self.version) < LooseVersion('1.115'): | ||
| jar_files.append('sam') | ||
| """All versions prior to 1.124 have these jar files""" |
There was a problem hiding this comment.
this shouldn't be a docstring, but a comment:
# all versions prior to 1.124 have these jar files|
@nathanhaigh: sanity check fails for existing Most likely because comparing We need a way around that, maybe by counting the digits in the minor version number? |
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1693/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
@nathanhaigh: ping on the issue with |
|
btw, apparently easybuilders/easybuild-easyconfigs#2572 was merged even though it requires this PR to be merged... seems like I was not very careful with testing easybuilders/easybuild-easyconfigs#2572, and it got tested on top of your modified easyblock... :( |
|
Actually, @boegel the version comparison works as expected: >>> from distutils.version import LooseVersion
>>> LooseVersion('1.39') < LooseVersion('1.124')
TrueI think the fail on picard 1.39 is because the following jars are not actually present: I'll update the easyblock. |
Some jar files were incorrectly assumed to be in picard versions < 1.124 but weren't. This broke installation of existing easyconfigs for the really old picard 1.39.
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1759/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
@nathanhaigh: I'm afraid picard 1.39 is still failing, see below... I have a feeling we're over-specifying this... The largest part of the easyblock now consists over making exceptions on which Is that really worth the trouble? Shouldn't we just check for a couple of key |
|
yep - I agree :) |
… different versions
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1768/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
retested with existing Thanks @nathanhaigh! |
Updated custom_paths for picard-1.124 and above
A restructure of picard at v1.124 means only a single
picard.jarfile is created