Provide option to use EESSI modules instead of init script#313
Provide option to use EESSI modules instead of init script#313casparvl wants to merge 14 commits into
Conversation
…erpret as comma-separated). Then, run the test suite on each version. Also: change how defaults are assigned in run_reframe.sh by using the ${X:-default_X} construct, which is more compact than what we currently have
…software is tested (in which looping over EESSI_VERSION should also not be done)
|
We will probably replace this by an alternative approach using ReFrame environments. Specifically, if you set: in the ReFrame config, and then use the upstream The regular hooks can then add additional features, and those will be repsected by reframe. E.g. if I hardcode: the above only runs on the subset of partitions that are marked with the "gpu" feature. |
…he programming environments as part of the ReFrame args first
…op_eessi_versions' into make_run_reframe_loop_eessi_versions
…ss extra options to reframe to limit to the programming environments that are specified. If both lists are emtpy, all programming environments are tested
…ame_loop_eessi_versions
|
Merged #326 into this, and succesfully ran with |
|
Ok, I need to dive back into this. On our AWS cluster (with no native module command): The job in the staging dir is: It seems that this doens't have the desired effect. Will have to dive into it, but no time now... |
|
Ok, the issue was a missing Succeeded: |
Make run_reframe.sh use EESSI modules. Also: change how defaults are assigned in run_reframe.sh by using the ${X:-default_X} construct, which is more compact than what we currently have.