First easystack for 2026.01 - #1546
Conversation
|
Let's check if the AWS bot has an updated config with 2026.06 targets now... bot:show_config |
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
| - GCCcore-15.2.0.eb | ||
| - Perl-5.42.0-GCCcore-15.2.0.eb: | ||
| options: | ||
| max-parallel: "1" |
There was a problem hiding this comment.
Should we do this in the hooks? Or is there a better fix for the tests so that we can fix it alltogether? Or is there an option just to disable the parallelism on the tests? (should be possible with a hook I guess?)
There was a problem hiding this comment.
Definitely better to do this in the hooks than here (just in case we'll rebuild things for another CPU target in the future, for example).
We should also add a comment to make it clear why this is necessary...
I think @bedroge has notes on that somewhere?
Installing the whole Perl easyconfig with just a single core will take a long time, which is a bit annoying, but not a showstopper. Would of course be nicer to only use a single core where it's really necessary...
|
bot: show_config |
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
See how far this gets. It'll need
2026.06module to be made available throughsoftware-layer-scripts.2026.06awareBased on Bob's easystack from https://gitlab.com/eessi/support/-/work_items/220#note_3478647043
Edit: It seems it doesn't need EESSI/software-layer-scripts#266 since that only provides a symlink. It should generate the module in the
/versionspecific directory itself, I suppose? Let's see... First, we need bot instances that are2026.06-aware.