-
Notifications
You must be signed in to change notification settings - Fork 209
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1919 from billsacks/compare_two_shorter_path
Shorter paths for case2 using system_tests_compare_two The recently-changed version of system_tests_compare_two nested case2's bld and run directories under $CIME_OUTPUT_ROOT/TESTNAME/case2/TESTNAME. Since the TESTNAME is often long, this was leading to very long paths to some things in the bld directory. This was causing some compilation errors. With this PR, case2's bld and run directories appear in $CIME_OUTPUT_ROOT/TESTNAME/case2/bld and $CIME_OUTPUT_ROOT/TESTNAME/case2/run. This shortens the bld directory paths enough to get some formerly-failing builds to pass. The change in run directory is just for consistency. I was hoping to do this just via setting EXEROOT and RUNDIR in system_tests_compare_two, to avoid cluttering up create_clone with arguments that are just needed for tests. But it turns out that we need to do this in create_clone, because create_clone calls case_setup, which creates the EXEROOT and RUNDIR directories. Test suite: scripts_regression_tests on cheyenne Also confirmed that the following tests build successfully: ERP.f10_f10_musgs.I1850Clm45BgcCru.yellowstone_pgi ERP_P60x2_Lm36.f10_f10_musgs.I2000Clm50BgcCrop.yellowstone_intel.clm-clm50cropIrrigMonth_interp Test baseline: N/A Test namelist changes: none Test status: bit for bit Fixes #1914 User interface changes?: none Update gh-pages html (Y/N)?: Code review: jedwards
- Loading branch information
Showing
6 changed files
with
113 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters