Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • mHM mHM
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 52
    • Issues 52
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mhmmhm
  • mHMmHM
  • Issues
  • #238
Closed
Open
Issue created Jan 03, 2023 by Peter Miersch@miersch

ExitCode still 0 after unsuccessful run

After an unsuccessful run of mHM with errors like

      Reading LAI ...
***ERROR: read_nc: mHM generated x and y are not matching NetCDF dimensions

or

    read precipitation        ...
***ERROR: length of time dimension needs to be at least 2 in file

it still exits with exitcode 0, suggesting that the run was successful. This makes monitoring and accounting of mHM runs more difficult, as the queuing system reports a successful run. This is especially a problem when running multiple instances of mHM parallelly. In contrast, when an input files is missing, mHM exits with exitcode 1, indicating that the run failed.

From my point of view, the ideal behavior would be that mHM exits with exitcode 1 if any error makes the run unsuccessful.

Assignee
Assign to
Time tracking