You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run GCHP 14.5.0 as a batch job, the GCHP log is empty, but the batch job log shows a segmentation fault.
It seems that GCHP is only being configured, but it hasn’t actually run, and the error occurs at that point.
A similar error also occurs when running interactively.
By the way, during compilation, some warnings were displayed, but it finally complete. I'm not sure whether these warnings could affect the GCHP run. So I also attached the environment file below.
What are the steps to reproduce the bug?
After compiling and setting up the run directory, when running GCHP as a batch job or interactively, the bug appears.
Please attach any relevant configuration and log files.
Your name
Yaqing Zhou
Your affiliation
Jinan University
What happened? What did you expect to happen?
When I run GCHP 14.5.0 as a batch job, the GCHP log is empty, but the batch job log shows a segmentation fault.
It seems that GCHP is only being configured, but it hasn’t actually run, and the error occurs at that point.
A similar error also occurs when running interactively.
By the way, during compilation, some warnings were displayed, but it finally complete. I'm not sure whether these warnings could affect the GCHP run. So I also attached the environment file below.
What are the steps to reproduce the bug?
After compiling and setting up the run directory, when running GCHP as a batch job or interactively, the bug appears.
Please attach any relevant configuration and log files.
gchp_log.txt
setCommonRunSettings.txt
batchjob_script.txt
batchjob_log.txt
gchp.env.txt
What GCHP version were you using?
14.5.0
What environment were you running GCHP on?
Local cluster
What compiler and version were you using?
Intel 2021.3.0
What MPI library and version were you using?
OpenMIPI 4.0.3
Will you be addressing this bug yourself?
No
Additional information
No response
The text was updated successfully, but these errors were encountered: