Noresm2 1 develop chem test

[annlew]

Summary: Test for checking functionality of --usr_mech_infile option for CAM_CONFIG_OPTS

Contributors: @annlew

Reviewers: @gold2718

Purpose of changes: Test to catch chemistry preprocessor failure

Github PR URL:

Changes made to build system: None

Changes made to the namelist: None

Changes to the defaults for the boundary datasets: None

Substantial timing or memory changes: None

Issues addressed by this PR:
cam_chempp issue with usr_mech_infile when path to compiler is too long (NorESMhub/CAM#160)

addresses NorESMhub/CAM#160

[TomasTorsvik]

Duplicates PR #545 , but for noresm2_1_develop branch.
Presumably, we want to include this in the noresm2.1.2 release?

[gold2718]

Duplicates PR #545 , but for noresm2_1_develop branch. Presumably, we want to include this in the noresm2.1.2 release?

Yes.

[TomasTorsvik]

@gold2718 - do you have a chance to look at this PR? I'm a bit concerned about the line

rm -f $CIMEROOT/../components/cam/chem_proc/campp

but on the other hand, the suggested mychems testmods is not part of the default testlist_allactive.xml. If I understand correctly, the mychems testmods will only be activated if the testlist_allactive.xml is changed, hence this PR should not change the default behavior?

[TomasTorsvik]

Since this PR only provides an optional setting for regression testing, I will approve it now. If a better solution is found, we can change this again later.