./case.setup ignores changes to env_batch.xml

[worleyph]

On Edison, if create a case (./create_newcase), execute ./case.setup, then change settings in env_batch.xml (like WALLTIME and QUEUE), then call ./case.setup again, the changes in env_batch.xml are not used to update case.run .

If I instead call ./case.setup -c followed by ./case.setup, then changes do take effect. However, this also sets BUILD_COMPLETE to .false. in env_build.xml.

According to @jgfouca , this is incorrect behavior, that ./case.setup should recognize and implement changes indicated in env_batch.xml.

[worleyph]

Note that I edited the env_batch.xml manually - I did not use xmlchange. Perhaps this is the reason that the change was not recognized?

[jgfouca]

I'll test that.

[worleyph]

Any progress? It is still happening in my recent Edison experiment.

[jgfouca]

@worleyph sorry this dropped off my radar. I will look at it today.

[jgfouca]

@worleyph , I tried this with both ESMCI and ACME and it doesn't matter if you run xmlchange or not, the case.run and case.test files will not get regenerated unless you clean the setup first.

I have a solution in mind that I'm going to propose to the ESMCI team.

[worleyph]

@jgfouca , thanks.

[jgfouca]

This issue is fixed by
ESMCI/cime#1039

On the ESMCI side.

[worleyph]

Reopening until fix is in place and tested in ACME.

[jgfouca]

This is now on master.