-
Notifications
You must be signed in to change notification settings - Fork 212
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
All component builds mislabeled as 'clm builds' #1223
Comments
Looks like the bug is in build.py@line:41 at
|
This patch should fix the problem,
|
@jgfouca : Is this the right fix? |
@jayeshkrishna , yes, putting it in now. |
You could also put this in the cime5.2.0 branch in ACME. Otherwise we'll have to live with it there for a while. |
As a CLM developer who is pretty much always only building CLM, I have to say I find this bug humorous. It sounds like you've discovered the evil plot of the CLM group to rule the world! Go CLM! And yes I am being sarcastic! ;-) |
The comment for that message says:
Should the message be more specific? All the components are built as libraries after all. And when the clm build is shared, who is it shared by? |
It's shared by multiple tests. |
Fix build model message Test suite: None (minor change) Test baseline: Test namelist changes: Test status: bit for bit Fixes #1223 User interface changes?: None Code review: @jedwards4b @jayeshkrishna
The ROF_NCPL was not compatible with ATM_NCPL, and the other NCPL settings were not set correctly for B compsets with ne4_oQU240 resolution. This fixes these issues. [BFB]
The ROF_NCPL was not compatible with ATM_NCPL, and the other NCPL settings were not set correctly for B compsets with ne4_oQU240 resolution. This fixes these issues. [BFB]
The ROF_NCPL was not compatible with ATM_NCPL, and the other NCPL settings were not set correctly for B compsets with ne4_oQU240 resolution. This fixes these issues. [BFB]
All component builds are labeled as clm builds.
I tried it on anlworkstation with master (cime5.3.0-alpha.02-9-g5f4f989) but should be an issue on other systems too.
The text was updated successfully, but these errors were encountered: