For feature/capgen: Update unit of ccpp_error_message from 1 to none as described in https://github.com/NCAR/ccpp-framework/issues/397. When these changes get merged back to main, the workaround in parse_checkers.py that is only in main, not in feature/capgen, must also be removed.
system tests:
I ran run_tests.sh in directory tests, all tests passed.
manual testing:
I tried to test this with the UFS. After removing the workaround in parse_checkers.py, the code generator tripped over the errflg mismatch that I just mentioned in https://github.com/ESCOMP/CCPPStandardNames/issues/19. A test with the UFS can only happen after this PR is merged into feature/capgen, and a reverse PR that updates main from feature/capgen and fixes errflg is created.
Update unit of
ccpp_error_message
from1
tonone
.For feature/capgen: Update unit of
ccpp_error_message
from1
tonone
as described in https://github.com/NCAR/ccpp-framework/issues/397. When these changes get merged back to main, the workaround inparse_checkers.py
that is only in main, not in feature/capgen, must also be removed.User interface changes?: No
Fixes : [Github issue #s] And brief description of each issue.
Testing: test removed: none unit tests: I ran the following doctests without failures:
system tests: I ran
run_tests.sh
in directorytests
, all tests passed.manual testing: I tried to test this with the UFS. After removing the workaround in
parse_checkers.py
, the code generator tripped over theerrflg
mismatch that I just mentioned in https://github.com/ESCOMP/CCPPStandardNames/issues/19. A test with the UFS can only happen after this PR is merged into feature/capgen, and a reverse PR that updates main from feature/capgen and fixeserrflg
is created.