Closed penguian closed 1 day ago
The segfault is possibly caused by a known error introduced in hdf5-1.14.3
that is fixed in hdf5-1.14.4
.
See https://github.com/HDFGroup/hdf5/issues/4381 and https://github.com/HDFGroup/hdf5/issues/3831
The following change in packages/mom5/package.py
results in a successful ACCESS-ESM1.5 pre-industrial
run:
[pcl851@gadi-login-09 spack-packages]$ git diff
diff --git a/packages/mom5/package.py b/packages/mom5/package.py
index a36c149..6309dde 100644
--- a/packages/mom5/package.py
+++ b/packages/mom5/package.py
@@ -45,6 +45,9 @@ class Mom5(MakefilePackage):
depends_on("libaccessom2~deterministic", when="~deterministic")
with when("@access-esm1.5"):
depends_on("oasis3-mct@access-esm1.5")
+ # Avoid segfault in HDF5 1.14.3
+ # https://github.com/HDFGroup/hdf5/issues/4381
+ depends_on("hdf5@:1.14.2,1.14.4:")
phases = ["edit", "build", "install"]
Can we close this issue then @penguian ?
Closed by #5 (when merged).
The ACCESS-ESM1.5
pre-industrial
configuration defined by access-esm1.5-configs, but using the executables created by the initial Spack environment defined by spack.yaml on the 2-spack-yaml branch, as per testing related to access-esm1.5-configs #16 fails with aSIGSEGV
segmentation violation in all 180 MOM5 ranks. The segmentation violation is in the HDF5H5T__init_native_float_types()
function, when opening a NetCDF4 file.