Add 2026.06 init scripts - #266
Open
casparvl wants to merge 13 commits into
Open
Conversation
casparvl
marked this pull request as draft
July 20, 2026 10:17
casparvl
changed the title
2 tasks
|
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
|
casparvl
changed the title
Contributor
Author
|
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
|
Contributor
Author
Seems fine, up until the loading of the module. |
Contributor
Author
|
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
Contributor
Author
|
bot:cancel job:178715 |
Contributor
Author
|
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
Contributor
Author
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
Contributor
Author
|
Don't want to wait for the node to boot and another one is free by now... bot:cancel job:178719 |
Contributor
Author
|
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
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
Contributor
Author
|
Bot:status last_build |
Contributor
Author
|
bot:status last_build |
|
This is the status of all the
|
9 similar comments
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
bedroge
approved these changes
Jul 30, 2026
Contributor
Author
|
Hmmm, Bob remarked that we should probably deploy this for bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 :)