Closed marshallward closed 7 months ago
Attention: Patch coverage is 0%
with 37 lines
in your changes are missing coverage. Please review.
Project coverage is 37.44%. Comparing base (
10521a9
) to head (f10ef1b
).:exclamation: Current head f10ef1b differs from pull request most recent head dc24883. Consider uploading reports for the commit dc24883 to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@jiandewang @DeniseWorthen are you able to provide a review for this sub-component PR? UFS-WM PR 2197 could be an option to test against soon.
thanks for @marshallward work. It eliminated those warning now.
@jiandewang testing is complete on UFS-WM PR #2202. Please merge this MOM6 PR when you're able.
just merged
This patch clears out many errors detected by Intel Fortran.
Most are false positives from stub functions which would normally be replaced in production and report unset output. These variables are now assigned dummy values in order to pacify the compiler.
The
stat
function in POSIX was incorrectly passing itsbuf
object to the Cstat
function asintent(in)
, causing the compiler to believe that the contents were unset. Oddly, this was already working correctly, and perhaps warrants further investigation, but it has now been correctly set tointent(inout)
.The
ppoly_*
variables incheck_reconstruction_1d
appear to have been incorrectly declared asout
, when they are clearly used asin
to validate the values. This has been corrected.register_diag_field
in the ice shelf diag manager was incorrectly declared and the function appeared to return nothing. Perhaps this function was not used for anything.An IO statement in MOM_open_boundary had a syntax error; this has been fixed.
get_dataset
returns adataset_type
, so some compilers expect the stub function to also return a validdataset
. Since the stubdataset_type
contains no fields, any locally declared instance should be sufficient as a return value.