Skip to content

Give a better error message for ESMF_Initialize after ESMF_Finalize#368

Merged
billsacks merged 1 commit into
developfrom
better_error_for_init_after_final
Apr 16, 2025
Merged

Give a better error message for ESMF_Initialize after ESMF_Finalize#368
billsacks merged 1 commit into
developfrom
better_error_for_init_after_final

Conversation

@billsacks

Copy link
Copy Markdown
Member

The previous error message in this case was more cryptic:

ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite().  Log message = Object being used after deletion  - Bad Object

The new error message is:

ESMF_FrameworkInternalInit: Cannot reinitialize ESMF after it has been finalized

This case seems hard (or maybe impossible) to test in the unit testing framework, but I have tested it with the code here:

https://github.com/billsacks/esmfprojects-multiple_esmf_initializes

The previous error message in this case was more cryptic:

   ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite().  Log message = Object being used after deletion  - Bad Object
@billsacks billsacks requested a review from oehmke March 26, 2025 17:33
@billsacks

Copy link
Copy Markdown
Member Author

@oehmke - I'd welcome a quick review whenever you get a chance

@anntsay

anntsay commented Apr 16, 2025

Copy link
Copy Markdown
Contributor

Team reviewed during core team meeting and approved this PR.

@billsacks billsacks merged commit 181ecf3 into develop Apr 16, 2025
@billsacks billsacks deleted the better_error_for_init_after_final branch April 16, 2025 16:01
@danrosen25 danrosen25 added this to the v08.09.00 milestone Apr 16, 2025
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.

3 participants