Open anton-seaice opened 2 months ago
This has been fixed in hdf5 1.14.4 - see https://github.com/HDFGroup/hdf5/pull/3837
The executables in
/g/data/ik11/spack/0.21.2/opt/linux-rocky8-cascadelake/intel-2021.10.0/access-om3-d6813d6b9e1df560ac3f6ba6a605daab9cfd9569_main-q4wfaqb
are built against hdf5@develop-1.14
which includes the above fix.
There are no DEBUG builds in that folder - I guess I would need to do a seperate debug build using those modules from that path ?
There are no DEBUG builds in that folder - I guess I would need to do a seperate debug build using those modules from that path ?
I may have misunderstood, when building through spack, the file name doesn't include Release/Debug like building though build.sh
. So possibly your executable would have fixed the problem.
This bug may no longer be relevant. With the ACCESS-NRI build, specifying build_type=Debug
doesn't flow down to the dependncies. i.e. the Debug flags are only on for compiling the access-om3 code (the bits in this repo and submodules) and not on for compiling hdf5.
When using the 0.3.0
Debug
build of OM3 (spack 0.21.2), @micaeljtoliveira found this error when running with the MOM6-CICE6 1deg_jra55do_iaf configThe run did not fail with the
Release
build.Debug sets
-fpe0
, so we believe there is a bug within the HDF5 library which causes the exception.A small (not quite minimal) example to reproduce the problem (Use
mpifort -fpe0
) :