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

Modern_diag_manger:: Use the correct date when prepending the date #1540

Merged
merged 5 commits into from
Jun 14, 2024

Conversation

uramirez8707
Copy link
Contributor

Description
Use the correct date when prepending the date

Fixes #1539

How Has This Been Tested?
CI, including new tests

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules
  • New check tests, if applicable, are included
  • make distcheck passes

Comment on lines +1016 to +1017
if (this%start_time .ne. diag_init_time) then
!> If the this%start_time is not equal to the diag_init_time from the diag_table
Copy link
Contributor

Choose a reason for hiding this comment

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

I only see a test where the date is prepended correctly. Is there a way to force this scenario to ensure it is caught?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The second test in test_prepend_date.sh should catch this.

diag_manager/fms_diag_file_object.F90 Show resolved Hide resolved
@rem1776 rem1776 merged commit b554b32 into NOAA-GFDL:release/2024.01 Jun 14, 2024
18 of 20 checks passed
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