CIME.tests.test_unit_compare_two.SystemTestsCompareTwoFake

class CIME.tests.test_unit_compare_two.SystemTestsCompareTwoFake(case1, run_one_suffix='base', run_two_suffix='test', separate_builds=False, multisubmit=False, case2setup_raises_exception=False, run_one_should_pass=True, run_two_should_pass=True, compare_should_pass=True)

Bases: SystemTestsCompareTwo

Methods

__init__	Initialize a SystemTestsCompareTwoFake object
build	Do NOT override this method, this method is the framework that controls the build phase.
build_indv	Perform an individual build
build_phase	This is the default build phase implementation, it just does an individual build.
clean_build
compare_env_run	Compare env_run file to original and warn about differences
copy_case1_restarts_to_case2	Makes a copy (or symlink) of restart files and related files (necessary history files, rpointer files) from case1 to case2.
run	Do NOT override this method, this method is the framework that controls the run phase.
run_indv	This fake implementation appends to the log and raises an exception if it's supposed to
run_phase	Runs both phases of the two-phase test and compares their results If success_change is True, success requires some files to be different

build(sharedlib_only=False, model_only=False, ninja=False, dry_run=False, separate_builds=False, skip_submit=False)

Do NOT override this method, this method is the framework that controls the build phase. build_phase is the extension point that subclasses should use.

build_indv(sharedlib_only=False, model_only=False)

Perform an individual build

build_phase(sharedlib_only=False, model_only=False)

This is the default build phase implementation, it just does an individual build. This is the subclass’ extension point if they need to define a custom build phase.

PLEASE THROW EXCEPTION ON FAIL

compare_env_run(expected=None)

Compare env_run file to original and warn about differences

copy_case1_restarts_to_case2()

Makes a copy (or symlink) of restart files and related files (necessary history files, rpointer files) from case1 to case2.

This is not done automatically, but can be called by individual tests where case2 does a continue_run using case1’s restart files.

run(skip_pnl=False)

Do NOT override this method, this method is the framework that controls the run phase. run_phase is the extension point that subclasses should use.

run_indv(suffix='base', st_archive=False, submit_resubmits=None, keep_init_generated_files=False)

This fake implementation appends to the log and raises an exception if it’s supposed to

Note that the Call object appended to the log has the current CASE name in addition to the method arguments. (This is mainly to ensure that the proper suffix is used for the proper case, but this extra check can be removed if it’s a maintenance problem.)

run_phase(success_change=False)

Runs both phases of the two-phase test and compares their results If success_change is True, success requires some files to be different