test script for acme_land_developer fail on edison

[jinyuntang]

The script for doing test acme_land_developer now fails on edison. It was fine last month before the new cime. Now it no longer works for me. I describe my experience in detail below.

With the following c-shell script, I successfully generated baseline.

#!/bin/csh -f

setenv MY_BASELINE_DIR /project/projectdirs/acme/jinyun/acme_baselines/

setenv PROJECT acme
setenv BASELINE_NAME 7a8187b
setenv TEST_ID ${BASELINE_NAME}

./create_test
acme_land_developer
--baseline-root ${MY_BASELINE_DIR}
-p ${PROJECT}
-b ${BASELINE_NAME}
-t ${TEST_ID}
-g
-v

However, when it failed when I use the following script to generate the case for comparison
#!/bin/csh -f

setenv MY_BASELINE_DIR /project/projectdirs/acme/jinyun/acme_baselines/

setenv PROJECT acme
setenv BASELINE_NAME 7a8187b
setenv TEST_ID git log -n 1 --format=%h

./create_test
acme_land_developer
--baseline-root ${MY_BASELINE_DIR}
-p ${PROJECT}
-b ${BASELINE_NAME}
-t ${TEST_ID}
-g
-v

The error message is as follows.

ERROR: Baseline directories already exists ['/project/projectdirs/acme/jinyun/acme_baselines/intel/7a8187b/ERS.f09_g16.I1850CLM45CN.edison_intel', '/project/projectdirs/acme/jinyun/acme_baselines/intel/7a8187b/ERS.f09_g16.IMCLM45BC.edison_intel', '/project/projectdirs/acme/jinyun/acme_baselines/intel/7a8187b/ERS.f19_f19.I1850CLM45CN.edison_intel', '/project/projectdirs/acme/jinyun/acme_baselines/intel/7a8187b/ERS.f19_f19.IM1850CLM45CN.edison_intel', '/project/projectdirs/acme/jinyun/acme_baselines/intel/7a8187b/ERS.f19_f19.IMCLM45.edison_intel', '/project/projectdirs/acme/jinyun/acme_baselines/intel/7a8187b/ERS.ne11_oQU240.I20TRCLM45.edison_intel', '/project/projectdirs/acme/jinyun/acme_baselines/intel/7a8187b/SMS.hcru_hcru.I1850CRUCLM45CN.edison_intel', '/project/projectdirs/acme/jinyun/acme_baselines/intel/7a8187b/SMS_Ly3_P1x1.1x1_smallvilleIA.ICLM45CNCROP.edison_intel.force_netcdf_pio']

[jgfouca]

Just add -o to your flags to create_test.

[jinyuntang]

@jgfouca, so this is on purpose to overwrite the baseline directories?

[jgfouca]

Yes, the old behavior was to silently blow away any previous baselines. The new behavior requires the user to specify -o.

[jinyuntang]

@jgfouca , Thanks, then I'll close the issue then.