-
Notifications
You must be signed in to change notification settings - Fork 371
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
Test failing with "ERROR: Requested field initialCarbon not available" #5204
Comments
@mark-petersen and @maltrud, I'm hoping you can help me figure this out, as this is one of my go-to tests. |
Thanks @xylar for reporting this. I reproduced this error. This is puzzling to me because it looks as if the carbon variables are in the package and streams exactly like the other conservation variables for energy, mass, and salt. I'll see if I can figure it out. |
Wow, that is really weird. There is an include line here:
and in the build directory for this run all the new carbon variables are in the
It writes these files new every time. I also tested with different order, putting Carbon variables first, but it is always |
The identical thing happens on cori, so this is not a strange i/o filesystem delay:
|
This does not happen with stand-alone, which uses make. E3SM uses cmake (though I can't imagine how that changes a simple include statement)
|
@philipwjones, any insight on the make vs. cmake difference in behavior? |
thanks for looking into this, @mark-petersen. I'm on board for blaming cmake. |
@xylar - could you please try this with "--project e3sm" in the create_test line? |
@jonbob, yes, that worked. Should I always use Also, why did that fix the problem, any idea? |
I'm seeing the same with |
As an aside, building on Anvil is much faster than on Chrysalis. Any idea why? |
I don't understand why that's true, but pretty much everyone sees how slow the build is on chrysalis. And I'll check out master and try the test again. Are you only seeing this with gnu? |
I'm testing with intel, not gnu. |
I tested a test merge of #5202 and it went fine. I'm trying to check out master again and re-test. |
The fact that @mark-petersen was able to reproduce this on both Chrysalis and Cori-Haswell makes me think it's not random but the fact that a test merge of #5202 with master worked fine really is leaving me confused. Is it consistent for a given branch but random for different branches?! |
A fresh check out of @mark-petersen, maybe take this as a lesson to start clean rather than trying to update |
I've also checked out master this morning and it seems to be fine on anvil, chrysalis and compy. |
I was able to confirm that this error does not occur with a fresh clone of master. What on odd problem, since the include files are created in the case build directory, which is recreated with each test. Well, that is something to remember. These all pass
|
Ha! I found it. There is a file stashed here that does not get updated, but appears to be used in the build:
In my directory that produces this error, the old Energy variables are there but the new Carbon variables are not:
@xylar if you have still have a local repo that produced this error, you should see the same thing. A fresh checkout does not have that file at all. I think this is caused by building MPAS-Ocean stand-alone, and then running E3SM jobs without a On a separate note, I noticed that some include files were inadvertently added to the repo in these |
Thanks @mark-petersen, that explains a lot! I was, indeed, using the same directory for standalone and E3SM testing.
I don't think that is correct. I think these are not auto-generated include files and that they are there intentionally to simplify code redundancy in the respective analysis members. |
I tried running the
ERS.ne11_oQU240.WCYCL1850NS.chrysalis_intel
test to check #5202. The command I used was:I am seeing error files:
that show:
It does seem that the analysis member is not enables:
The field
initialCarbon
is, indeed, in the streams file:but as I understand it, this should be fine. If the package is disabled, this field simply shouldn't be allocated or written out.
The text was updated successfully, but these errors were encountered: