Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some vars resolve too early #406

Closed
rljacob opened this issue Aug 16, 2016 · 1 comment · Fixed by #414
Closed

Some vars resolve too early #406

rljacob opened this issue Aug 16, 2016 · 1 comment · Fixed by #414
Assignees

Comments

@rljacob
Copy link
Member

rljacob commented Aug 16, 2016

Reported by @jedwards4b:
Some variables in env_*.xml files are being resolved too early - this results in a number of problems including one found by John Truesdale: If the variable CASE is defined in the environment when you ran create_newcase then the EXEROOT and RUNDIR would be defined using the CASE from the environment instead of the one in the create_newcase argument.

@mnlevy1981
Copy link
Contributor

Closed #326 because it seems to be the same issue as this ticket -- $CIMEROOT is also picked up by create_newcase if it is in your environment. From talking with @jedwards4b it seems like some CIME scripts (configure, for example) do need CIMEROOT in your environment (and create_newcase needs other environment variables such as $USER), but perhaps there is a way to limit which scripts look for which variables in the environment?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants