{2023.06}[2023a] bcgTree 1.2.1#1032
Conversation
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:aarch64/neoverse_v1 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
The sanity check of MUSCLE is failing: |
|
The release noted of MUSCLE suggest that they support Aarch64, See https://github.com/rcedgar/muscle/releases/tag/v5.1. But the failure suggests otherwise. I found this in their |
|
A LLM says I should try this and it does not seem crazy. (Asked him what is wrong with this line LLM: |
|
Tested this pr, easybuilders/easybuild-easyconfigs#22780, on the neoverse_v1 node and than it completed the build. |
laraPPr
left a comment
There was a problem hiding this comment.
Pick-up MUSLE with patch for Aarch64
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:aarch64/neoverse_v1 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
Ok got through 2 out of the 4 builds with the patch to MUSCLE |
|
RAxML failed |
Co-authored-by: Bob Dröge <b.e.droge@rug.nl>
|
Label |
|
Label |
1 similar comment
|
Label |
|
Label |
|
Hmm, the missing installation CI is failing for the Arm targets because edit: I guess we need to do something similar as we do for LAMMPS (https://github.com/EESSI/software-layer/blob/2023.06-software.eessi.io/eb_hooks.py#L376) and CP2K (https://github.com/EESSI/software-layer/blob/2023.06-software.eessi.io/eb_hooks.py#L394), because the checks are running on x86_64? Or maybe we could use a native Arm runner for the Arm targets, but I'm not sure how easy it is to split the CI. |
Seems like it boils down to using a different That doesn't seem very difficult to do, see https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#example-using-a-multi-dimension-matrix I'll take a quick stab at it, this PR is a good excuse to look into that (and it's a good test case). |
|
@bedroge Turns out it's not that difficult, see: |
|
synced with updated |
|
PR merged! Moved |
|
PR merged! Moved |
|
PR merged! Moved |
|
PR merged! Moved |
|
PR merged! Moved |
|
PR merged! Moved |
4 out of 39 required modules missing: