search

EESSI / software-layer

Software layer of the EESSI project
https://eessi.github.io/docs/software_layer
GNU General Public License v2.0
24 stars 48 forks source link

`EESSI-extend` and `configure_easybuild` no longer in sync #802

Open ocaisa opened 3 weeks ago

ocaisa commented 3 weeks ago

https://github.com/EESSI/software-layer/pull/710 introduced a change in configure_easybuild to support accelerators but this change has not been incorportated into EESSI-extend. It's not entirely clear how we want to do this either since EESSI-extend supports 4 different scenarios (CVMFS, site, project, user).

Do we want this distinction to apply in all cases? This introduces complexity as the behaviour of the module will depend on whether or not the trigger environment variable (EESSI_ACCELERATOR_TARGET) is set or not, and for the end user there are no protections in place to stop them accidentally installing a CPU build into an accelerator target space. The only "person" automatically setting EESSI_ACCELERATOR_TARGET is the bot, so I think this bit of logic is best suited to the bot build scripts (unless we put protections in place in our EB hooks).

ocaisa commented 3 weeks ago

I guess we could support this for EESSI and site installations since we control the exposure of those module trees.

For the site case, I would probably disable --robot in this case and issue a warning that this has been done so they do not accidentally install CPU-only dependencies into the accelerator stack