Skip to content
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

add esmf_logmsg to shr_abort #62

Merged
merged 5 commits into from
Jan 24, 2025

Conversation

jedwards4b
Copy link
Contributor

Adds a call to esmf_logmsg to share abort mod so that both the PET files and component logs are updated with the error message.

Fixes #61

@jedwards4b jedwards4b self-assigned this Jan 23, 2025
@jedwards4b jedwards4b merged commit 2bb87b8 into ESCOMP:main Jan 24, 2025
1 check passed

call print_error_to_logs("ERROR", local_string)

call ESMF_LogWrite(local_string, ESMF_LOGMSG_ERROR, line=line, file=file)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jedwards4b question. What will happen if line and/or file aren't present in the call and they are sent down this way to ESMF_LogWrite? It seems like it might be compiler dependent on how it handles passing down a non-present argument.

But, I'm interested if you did any testing around that. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add options to shr_abort_abort for reporting errors to ESMF logging
3 participants