-
Notifications
You must be signed in to change notification settings - Fork 66
{2023.06}[2023b,a64fx] apps originally built with EB 4.9.2 #1151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion architecture:aarch64/a64fx |
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion architecture:aarch64/a64fx |
|
@hvelab We have updated the bot on Deucalion to v0.9.0, which includes a breaking change w.r.t. build commands. So use It's probably wise to hold off on re-triggering builds for A64FX until this fix is merged: |
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx |
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx |
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx |
|
New job on instance
|
| options: | ||
| # see https://github.com/easybuilders/easybuild-easyconfigs/pull/21366 | ||
| # use the latest update of the bundle | ||
| from-commit: 743dcc4e3440f29200b90a3cd1aaee2580aaf19f |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this commit is too recent (from EB 5.x), and it will probably use easyconfigs for dependencies from this same commit, causing failures (in this particular case for GDAL, I guess because PYTHONPATH is not explicitly set anymore). Maybe it's better to stick to an older one, e.g. one that was used for grace or sapphirerapids.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The older commits "work" but checksums fail for some extensions, what's the correct way to proceed here? I pick the recipe for an older commit, fix the checksums and make a PR for EB with maybe a different name or some way to differentiate it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, that's tricky indeed... Maybe you could still use the latest commit then, but in order to prevent build failures of the dependencies (e.g. GDAL), those would have to use an older commit (e.g. the one that we used for sapphirerapids: https://github.com/EESSI/software-layer/blob/main/easystacks/software.eessi.io/2023.06/sapphirerapids/eessi-2023.06-eb-4.9.2-2023b.yml#L27).
Alternatively, we could build the R bundle and its dependencies with a newer EB version. Then we won't build everything in the exact same way as for the other CPUs, but it's much easier to do it that way.
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx |
|
New job on instance
|
|
It now failed because of a checksum error for the bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx |
|
New job on instance
|
|
Looks like it worked!! I cannot edit the labels to put the deploy one |
|
@hvelab I added it (you wouldn't deploy your own PRs anyway, better to leave that to another pair of eyes) |
|
Ingested |
Based on #989