{2025.06-001}[2025b] netCDF 4.9.3 (LAMMPS dependency)#72
{2025.06-001}[2025b] netCDF 4.9.3 (LAMMPS dependency)#72bedroge merged 13 commits intoEESSI:mainfrom
Conversation
|
bot: build repo:dev.eessi.io-riscv-2025.06-001 instance:eessi-bot-riscv for:arch=riscv64/generic |
|
New job on instance
|
|
This is the error in the logs: |
|
libxml2 was added as an explicit dependency to netCDF here: easybuilders/easybuild-easyconfigs@3f74f3b But it is not being considered here: https://github.com/easybuilders/easybuild-easyblocks/blob/c0b3a8983af664f7226eaa9e503840f6b8c3bbf2/easybuild/easyblocks/n/netcdf.py#L71 I think this is causing trouble because the build of netCDF is mixing two libxml2 installations (versions):
|
|
@bedroge , what do you think? |
I think your explanation makes sense. I only wondered why we hadn't seen this with |
|
bot: build repo:dev.eessi.io-riscv-2025.06-001 instance:eessi-bot-riscv for:arch=riscv64/generic |
|
New job on instance
|
|
The build passes, but the tests are failing due to this again: That seems to happen for all build jobs on premier that do something with MPI... |
|
Admins suggested me to add: So adding these exports into |
|
bot: build repo:dev.eessi.io-riscv-2025.06-001 instance:eessi-bot-riscv for:arch=riscv64/generic |
|
New job on instance
|
|
Tested with a simple HelloWorld testcase, and |
|
Ah, great! |
|
It looks like the sourcing of that site_config script may not work, I think it's related to running in the dev repo. I'll look into it. |
|
bot: build repo:dev.eessi.io-riscv-2025.06-001 instance:eessi-bot-riscv for:arch=riscv64/generic |
|
New job on instance
|
|
bot: build repo:dev.eessi.io-riscv-2025.06-001 instance:eessi-bot-riscv for:arch=riscv64/generic |
|
New job on instance
|
|
@bedroge , 3 tests failing with the same PMIX error as before. We need the sourcing of |
|
Oh, right, I forgot about that. The site config script would not work for this, unfortunately, as the build script sort of wipes the environment again. An alternative would be using Lmod hooks for this, but I couldn't immediately get that to work, as it's looking in a non-existing location in the dev repo. I can try to come up with a fix for that by making a symlink. |
|
EESSI/filesystem-layer#267 should fix this and allow us to use site-specific Lmod hooks for dev.eessi.io. |
|
bot: build repo:dev.eessi.io-riscv-2025.06-001 instance:eessi-bot-riscv for:arch=riscv64/generic |
|
New job on instance
|
No description provided.