{2023.06}[2023a] cutadapt 4.9 (testing staging bundles)#91
{2023.06}[2023a] cutadapt 4.9 (testing staging bundles)#91trz42 wants to merge 33 commits into2023.06-software.eessi.iofrom
Conversation
update commits
…ill be used by the bootstrap of load_easybuild_version anyway
use latest commit of merged prs for MUSCLE and bcgTree
{2023.06}[SYSTEM,icelake+cascadelake] EasyBuild 4.8.2 + 4.9.0 + 4.9.1 + 4.9.4 + 5.0.0, EESSI-extend
|
Instance
|
…-layer into test_staging_bundles
|
bot: build instance:eX3-dev-310 repo:eessi.io-2023.06-software arch:x86_64/amd/zen2 |
Updates by the bot instance
|
|
New job on instance
|
|
bot: help |
Updates by the bot instance
|
|
bot: show_config |
Updates by the bot instance
|
|
Instance
|
|
bot: build instance:aws-dev-310 repo:eessi.io-2023.06-software arch:x86_64/amd/zen2 |
Updates by the bot instance
|
|
New job on instance
|
|
bot: build instance:aws-dev-310 repo:eessi.io-2023.06-software arch:x86_64/generic |
Updates by the bot instance
|
|
New job on instance
|
|
bot: build instance:aws-dev-310 repo:eessi.io-2023.06-software arch:x86_64/amd/zen2 |
…efixes. This hook has caused more issues than it's worth, and the warning has been there for a long time now, so people should know.
…4.12.2-GCCcore-12.3.0-Python-3.11.3
{2023.06}[2023a,grace] Z3 v4.12.2
…fix_lmod_hook Remove eessi startup hook that errors on CUDA being moved from CPU prefixes
{2023.06}[SYSTEM,icelake+cascadelake] EasyBuild 4.9.2 + 4.9.3
Co-authored-by: Bob Dröge <b.e.droge@rug.nl>
… for aarch64/* CPU targets
…on for aarch64/* targets to pass when using an x86_64 GitHub Actions runner, no longer needed due to 74b6b85
|
Builds failed because of the CUDA Lmod check (should be fixed now) and the missing |
Updates by the bot instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
…-layer into test_staging_bundles
|
Build again... |
Updates by the bot instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
This PR doesn't work at all. |
|
PR merged! Moved |
Build something small (?) for several architectures and verify if bundling of tarballs into single staging PR works as intended.