Add 2026.06 symlink#266
Conversation
|
bot: status |
|
This is the status of all the
|
3 similar comments
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
Seems fine, up until the loading of the module. |
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
…cripts into 2026.06-module
|
bot:cancel job:178715 |
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
… UMASK. That doesn't make sense for some scripts that NEED to be executable, such as
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
Don't want to wait for the node to boot and another one is free by now... bot:cancel job:178719 |
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
We should discuss in tomorrow's support meeting if we want to start exposing
2026.06.Also, before building, we need the bots to be configured to build for 2026.06 (https://github.com/EESSI/bot-configs/pull/97)
Edit: this was discussed in the support meeting today, there was consensus to not yet put this symlink in place, we only put the module in place in the
/version/2026.06specific directory. I think that will be created if we trigger builds on EESSI/software-layer#1546Edit2: my bad, we can (and should) do this PR. The symlink in
/cvmfs/software.eessi.io/initis made from the filesystem-layer side. This PR would create a symlink in/cvmfs/software.eessi.io/versions/2026.06/init/modules/EESSI, which is indeed what we need right now :)