-
Notifications
You must be signed in to change notification settings - Fork 209
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
ERI test creates more sym links than it needs to #1325
Labels
Comments
fischer-ncar
pushed a commit
that referenced
this issue
Apr 11, 2017
Update number of nodes passed to Mira qsub: CIME 5.2 fixed $TOTALPES, which was incorrect in CIME 5.1. This sets the number of nodes passed to qsub as $TOTALPES/$PES_PER_NODE. [BFB]
jedwards4b
added a commit
that referenced
this issue
May 17, 2017
link only hybrid files from ref2 We only need to link hybrid hist files from the ref2 run directory to the original run directory, other hist files wiill be copied from the archive rest directory if required. Test suite: scripts_regression_tests.py ERI.T62_g37.G.cheyenne_intel.pop-cice Test baseline: Test namelist changes: Test status: bit for bit Fixes #1325 User interface changes?: Code review:sacks
ghost
removed
the
in progress
label
May 17, 2017
jgfouca
pushed a commit
that referenced
this issue
Feb 23, 2018
Update number of nodes passed to Mira qsub: CIME 5.2 fixed $TOTALPES, which was incorrect in CIME 5.1. This sets the number of nodes passed to qsub as $TOTALPES/$PES_PER_NODE. [BFB]
jgfouca
pushed a commit
that referenced
this issue
Mar 13, 2018
Update number of nodes passed to Mira qsub: CIME 5.2 fixed $TOTALPES, which was incorrect in CIME 5.1. This sets the number of nodes passed to qsub as $TOTALPES/$PES_PER_NODE. [BFB]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The ERI test creates a bunch of unnecessary sym links in the main case (i.e., the case without a 'ref' extension), pointing to history files in the ref2 archive space. As far as I can tell, this doesn't cause problems with the test, but it makes it hard to understand what's going on when you're trying to debug a failed test: It means that the history files created by the main case are actually put in the ref2 archive space! I could also imagine this causing problems in some edge cases, e.g., involving rerunning a test, but I'm not sure about that.
Specifically, I ran
ERI_Lm36.T31_g37_gl4.IGCLM45.yellowstone_intel.clm-glcMEC_long
, but this should show up in many ERI tests.It looks like these come from this code in eri.py:
This block follows immediately after:
and I would think that that
_helper
is enough to create the necessary sym links to run the main case.@jgfouca @mvertens @jedwards4b - it looks like you're the ones who wrote the python version of this test. Can any of you comment on this?
The text was updated successfully, but these errors were encountered: