add support to ConfigureMake for tweaking (first part of) test command via 'test_cmd'#2726
Conversation
|
Test report by @ocaisa Overview of tested easyconfigs (in order)
Build succeeded for 1 out of 1 (1 easyconfigs in total) |
|
@boegel Interestingly, if I use this (with but if I do the same thing in extended dry run mode, it reports the default: That's because the easyblock git patch is never actually applied, which I think would perhaps not be expected. I'll open an issue for that. |
|
Test report by @boegel Overview of tested easyconfigs (in order)
Build succeeded for 11 out of 11 (11 easyconfigs in total) |
| @@ -348,7 +350,12 @@ def test_step(self): | |||
| """ | |||
|
|
|||
| if self.cfg['runtest']: | |||
There was a problem hiding this comment.
@boegel Hm, i just realized this leads the situation that you need to specify something in the runtest part, else testing won't be considered.
Perhaps change this to
if self.cfg['runtest'] or self.cfd['test_cmd'] != DEFAULT_TEST_CMD:Otherwise you'd have to do possibly silly things:
test_cmd = './tests.sh'
runtest = ' ' # only to trigger the testsor
test_cmd = 'ctest'
runtest = '-j' # add one flag here or something to make it actually run.There was a problem hiding this comment.
@Micket Makes sense, please open a PR for that ASAP, maybe (just maybe) we can still include this into EasyBuild v4.5.5
No description provided.