-
Notifications
You must be signed in to change notification settings - Fork 250
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
Regression tests that are not looking for specific output files can fail silently #23
Comments
This issue is avoided for the ufs_public_release branches only in #25 by explicitly checking for output files from the DEBUG tests. |
Dom, Do you still want to work on this issue, or if we can close it? |
I think this needs to be fixed for the develop branch - all debug tests should look for specific output files. |
I see, will add output files for debug tests in the next develop branch
commit.
…On Wed, Feb 19, 2020 at 11:02 AM Dom Heinzeller ***@***.***> wrote:
I think this needs to be fixed for the develop branch - all debug tests
should look for specific output files.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#23?email_source=notifications&email_token=AI7D6TMKRFNIG2B22IN3HTTRDVJ3FA5CNFSM4KBNRB72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMIK4HA#issuecomment-588295708>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TNASWCXMMCX7WQSTILRDVJ3FANCNFSM4KBNRB7Q>
.
|
…d_data_structures gsd/develop: handle blocked data structures in init and finalize routines, remove pset logic, metadata cleanup
@junwang-noaa do you know if this has been fixed, i.e. are all DEBUG tests looking for output files nowadays? I know that all the DEBUG tests I put in do. |
Sorry, not yet. We still need to add output files
for fv3_ccpp_control_debug and fv3_ccpp_stretched_nest_debug.
…On Wed, Oct 21, 2020 at 10:03 AM Dom Heinzeller ***@***.***> wrote:
@junwang-noaa <https://github.com/junwang-noaa> do you know if this has
been fixed, i.e. are all DEBUG tests looking for output files nowadays? I
know that all the DEBUG tests I put in do.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TJUR2NOZQA3UIKTCT3SL3S3XANCNFSM4KBNRB7Q>
.
|
…led model (#254) * Implements a bugfix for the mapping of ifrac for both nems_orig and nems_frac in CMEPS: issue (#17)[NOAA-EMC/CMEPS#17] * Adds field-packing for performance improvements in CMEPS: issue (#23)[NOAA-EMC/CMEPS#23] * Uses module file fv3_debug when DEBUG=Y is specified and fv3_debug is available * Shortens the nems.configure file name used with the coupled model
Closed via 248b609 |
Some of the DEBUG regression tests do not check for the presence of output files generated by the model, the idea being that the code should just run and complete without an error. However, even if the code crashes rt.sh still thinks that the model ran ok (see issue #24 for an example).
The text was updated successfully, but these errors were encountered: