Conversation
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen3 |
|
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
|
|
Had a quick look at the neoverse v1 logs, looks like it ran out of memory, found several of these messages: |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=aarch64/generic |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
Looks like it still runs out of memory on neoverse n1: Let's try it one more time, and otherwise we'll have to reduce the number of cores to even less than 8. bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=aarch64/neoverse_n1 |
|
New job on instance
|
|
I don't understand why it worked in EESSI/software-layer-scripts#139 (comment), but here I still get out of memory errors, also for neoverse v1: |
|
Different message, but probably the same problem for the a64fx build: |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=aarch64/generic |
|
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 PR is ready, but let's wait with the deployment until #1346 has been ingested and the bucket has been cleaned. |
|
Cleaned the buckets, this should be good to go now. |
|
staging PR merged |
Uh oh!
There was an error while loading. Please reload this page.