-
Notifications
You must be signed in to change notification settings - Fork 213
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
Confusing BASELINE result: PASS but also "Could not interpret CPRNC output" #4685
Comments
I reran this and got the same message. I'm also seeing the same message in a lot of the tests that @fischer-ncar has been running recently. |
I'm seeing these messages too. But didn't notice them since it was the BASELINE was passing. |
Comments passed to hist_utils:get_ts_synopsis are
I see no reason for this to trigger the "Could not interpret CPRNC output" - except that as far as I can tell the comment should not have been passed in at all? @jasonb5 |
I see the issue the catch-all is |
Thanks a lot @jasonb5 ! |
@jasonb5 While running our CAM regression tests, I'm encountering these
I'm well outside my understanding of the code, but maybe we also need to check for "PASS"? |
I'm confused by the TestStatus I'm seeing in a test I just ran with baseline comparisons:
There are two things that I find confusing about this:
(1) It's not clear to me what CPRNC output is leading to this "Could not interpret" message. I'm attaching the TestStatus.log file here. At a glance, it looks like all cprnc output is showing typical "IDENTICAL" lines.
TestStatus.log
(2) If it's really the case that there's at least one CPRNC file for which the code can't interpret the output, I feel like it would be safest to mark the result as a FAIL rather than a PASS, so that this isn't overlooked.
It looks like @jasonb5 introduced this in e33bede, so Jason, I'm assigning this to you in hopes that you can help clarify this for me.
The text was updated successfully, but these errors were encountered: