-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial Spack env fails with segfault in MOM5 #6
Comments
The segfault is possibly caused by a known error introduced in |
The following change in
|
Can we close this issue then @penguian ? |
Closed by #5 (when merged). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.The text was updated successfully, but these errors were encountered: