Set snellius zen4 override #187
Conversation
| @@ -63,7 +63,10 @@ | |||
| { | |||
| 'name': 'genoa', | |||
| 'scheduler': 'slurm', | |||
| 'prepare_cmds': [common_eessi_init()], | |||
| 'prepare_cmds': [ | |||
| 'export EESSI_SOFTWARE_SUBDIR_OVERRIDE=x86_64/amd/zen4', | |||
There was a problem hiding this comment.
what does this do exactly?
There was a problem hiding this comment.
Make sure that on our Genoa nodes, the zen4 stack is used. The EESSI init script currently falls back on zen3, since the zen4 stack is not 'complete' yet (it doesn't have all the modules that are there for zen3, though it's getting pretty close). I don't want that fallback, I really want to test the zen4 stack :)
You'll find the same in our azure_mc.py config, that's the build cluster for our zen4 stuff.
There was a problem hiding this comment.
Note that it also doesn't hurt to hard code those overrides if you know what partition you are on. It simply means you're not relying on the autodetection in the init script (but I know the hardware in this partition, so that's ok :P)
No description provided.