{2026.06}[foss/2026.1] First easystack for 2026.01: GCCcore/15.2.0 - #1546
Merged
Conversation
Collaborator
Author
|
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
|
Collaborator
Author
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
casparvl
commented
Jul 28, 2026
| - GCCcore-15.2.0.eb | ||
| - Perl-5.42.0-GCCcore-15.2.0.eb: | ||
| options: | ||
| max-parallel: "1" |
Collaborator
Author
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?)
Contributor
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...
Member
|
bot: show_config |
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
Collaborator
|
Let's just give this a try to check if all prerequisites are in place now: bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
casparvl
commented
Jul 31, 2026
|
This is the status of all the
|
6 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
|
Contributor
|
Let's see if building for Graviton 4 works (bot in bot: build repo:eessi.io-2026.06-software instance:eessi-bot-aws-eu-south for:arch=aarch64/aws/graviton4 |
|
New job on instance
|
casparvl
marked this pull request as ready for review
August 4, 2026 11:53
Collaborator
Author
|
bot:status last_build |
|
This is the status of all the
|
8 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
|
boegel
changed the title
GCCcore/15.2.0
boegel
added
bot:deploy
casparvl
commented
Aug 4, 2026
Co-authored-by: Caspar van Leeuwen <33718780+casparvl@users.noreply.github.com>
Contributor
|
staging PR merged |
boegel
approved these changes
Aug 4, 2026
casparvl
changed the title
GCCcore/15.2.0GCCcore/15.2.0
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
4 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.
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.