{2025.06}[2025b] PETSc + SLEPc + petsc4py + slepc4py 3.24.0 - #1608
{2025.06}[2025b] PETSc + SLEPc + petsc4py + slepc4py 3.24.0#1608boegel wants to merge 2 commits into
Conversation
boegel
commented
Sep 2, 2026
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/generic |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-aws-eu-south for:arch=x86_64/amd/zen5 |
|
New job on instance
|
|
Hmm, persistent failure on test step for PETSc is failing, but no clear errors in output file; EasyBuild log looks a bit weird too with lots of line wrapping: I wonder if terminal width somehow has something to do with it here... I'll kick off an interactive build on |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
Unable to download or merge changes between the source branch and the destination branch. |
|
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
|
|
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
|
manual installation (using |
|
for let's try that one again... bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen3 |
|
New job on instance
|
|
For the bot build of |
|
@boegel for zen5 job 324 I see this at the bottom of the log: So it probably ran out of memory and crashed the node, then Slurm restarted it automatically, and it started running in the same job dir again. |
OK, I totally missed that. Why would we only see a problem with memory for the Unless this has something to do with it: Do our |
|
Let's see if the failure for bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/intel/haswell |
|
New job on instance
|
|
@bedroge Let's cut down number of cores used for building/testing PETSc in half: |