-
Notifications
You must be signed in to change notification settings - Fork 236
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
Nuopc api test #1292
Nuopc api test #1292
Conversation
- Allows us to check that we have not broken the ability to compile with the NUOPC, MCT or coupled_driver modules. - This is not a complete compile but only upto the last module that does not need anything other than MOM6 objects.
- Following suggestion from @marshallward I've implemented an option to select the driver code at the configure stage (changes to configure.ac) - This allows the target build/coupled/ocean_model_MOM.o to be built using the .testing ac tools.
- Checks that MOM6 can be compiled with the various coupled drivers.
- We spent 1 minute build symmetric unnecessarily when checking the coupled APIs
Codecov Report
@@ Coverage Diff @@
## dev/gfdl #1292 +/- ##
============================================
- Coverage 45.88% 45.82% -0.07%
============================================
Files 225 227 +2
Lines 71396 71552 +156
============================================
+ Hits 32763 32791 +28
- Misses 38633 38761 +128
Continue to review full report at Codecov.
|
To the surprise of no one, this PR passed the MOM6 pipeline testing at https://gitlab.gfdl.noaa.gov/ogrp/MOM6/-/pipelines/11882. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks good to me, and it has passed all of our tests.
--with-driver=<path_to_driver>
and new targets (e.g. check_mom6_api_nuopc, check_mom6_api_coupled) to.testing/Makefile
to facilitate the above.