-
Notifications
You must be signed in to change notification settings - Fork 92
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
coupler history file fails exact restart #88
Comments
I poked at this a bit. Since the merged change incorporates three different bug fixes, I think the sanest way to debug the issues is going to be to back them out one at a time to narrow down the problem. For now I'm going to mark this test as an expected fail. |
Good plan, thanks for looking into this On Mon, Aug 1, 2016 at 3:54 PM, Ben Andre [email protected] wrote:
|
Note: this was reproducible in the original merge, but was an unexpected pass in 203bb6a. |
closing, presumed fixed with 203bb6a. |
into andre-ed-clm-16x based on clm-r181 Test suite: ed - yellowstone gnu, intel, pgi clm-short - yellowstone gnu, intel, pgi Testing: all clm_short tests pass. One new expected failure in the 'ed' test suite. Coupler history file is no longer bit for bit on restart, see #88.
andre-ed-clm-16x. Test suite: ed - yellowstone intel, gnu, pgi clm_short - yellowstone intel, gnu, pgi Test baseline: none, orginial branch was answer changing. Test status: all tests pass. expected fail in #88, ERS_D ICLMED yellowstone_gnu unexpectedly passed.
into andre-ed-clm-16x based on clm-r181 Test suite: ed - yellowstone gnu, intel, pgi clm-short - yellowstone gnu, intel, pgi Testing: all clm_short tests pass. One new expected failure in the 'ed' test suite. Coupler history file is no longer bit for bit on restart, see #88.
andre-ed-clm-16x. Test suite: ed - yellowstone intel, gnu, pgi clm_short - yellowstone intel, gnu, pgi Test baseline: none, orginial branch was answer changing. Test status: all tests pass. expected fail in #88, ERS_D ICLMED yellowstone_gnu unexpectedly passed.
Summary of Issue:
The merge of c0654db into the clm-trunk merge branch introduced a change that causes the coupler history file to not be bit for bit on a single restart test.
Failing fields from TestStatus.log
Note: This test is part of the 'ed' suite. All tests in the
clm_short
suite pass for yellowstone intel, gnu, pgi.Expected behavior and actual behavior:
Prior to this change, all tests in the 'ed' and 'clm_short' test suites were passing, they should continue to pass with these changes.
Steps to reproduce the problem (should include create_newcase or create_test command along with any user_nl or xml changes):
What is the changeset ID of the code, and the machine you are using:
264dd21, yellowstone, gnu
The text was updated successfully, but these errors were encountered: