Repository navigation
{2026.06} EasyBuild v5.4.1 - #1793
Conversation
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=aarch64/neoverse_n1 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
bot:status last_build |
|
This is the status of all the
|
4 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
|
3 similar comments
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
|
The RISC-V tarball wasn't uploaded: #1793 (comment) I'm not sure if this is usually the case or if something went wrong here |
I never ran into this before, I'm not sure how to proceed here. @boegel, any ideas? |
@Neves-P We can try triggering a new build & deploy, but if that also fails, I wouldn't hold this back, since it's for RISC-V, which is not a primary CPU target yet... |
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-riscv-prod for:arch=riscv64/generic |
|
New job on instance
|
|
@Neves-P ready to re-trigger deploy for RISC-V build |
|
Doesn't seem to have worked, @boegel :(. I'd say let's just ingest it. |
|
@Neves-P transfer failed again, so I propose we follow-up on this via a dedicated PR for RISC-V... |
|
Agreed. Staging PR merged, as for the other EESSI versions. I'd already reviewed the staging bundle PRs yesterday (minus RISC-V here) |
Solved (bot was using a |
No description provided.