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

All component builds mislabeled as 'clm builds' #1223

Closed
jayeshkrishna opened this issue Mar 9, 2017 · 8 comments
Closed

All component builds mislabeled as 'clm builds' #1223

jayeshkrishna opened this issue Mar 9, 2017 · 8 comments

Comments

@jayeshkrishna
Copy link
Contributor

All component builds are labeled as clm builds.

Component csm_share build complete with 3 warnings
         - Building clm Library 
Building atm with output to /homes/jayesh/acme/scratch/test_X_f19_g16/bld/atm.bldlog.170309-084354
         - Building clm Library 
Building lnd with output to /homes/jayesh/acme/scratch/test_X_f19_g16/bld/lnd.bldlog.170309-084354
...

I tried it on anlworkstation with master (cime5.3.0-alpha.02-9-g5f4f989) but should be an issue on other systems too.

@jayeshkrishna
Copy link
Contributor Author

Looks like the bug is in build.py@line:41 at

        else:
            logger.info("         - Building clm Library ")


@jayeshkrishna
Copy link
Contributor Author

This patch should fix the problem,

diff --git a/scripts/lib/CIME/build.py b/scripts/lib/CIME/build.py
index 3bbf2c1..6aa1be8 100644
--- a/scripts/lib/CIME/build.py
+++ b/scripts/lib/CIME/build.py
@@ -38,7 +38,7 @@ def _build_model(build_threaded, exeroot, clm_config_opts, incroot, comp
                 else:
                     continue
         else:
-            logger.info("         - Building clm Library ")
+            logger.info("         - Building %s Library ", model)
 
         smp = nthrds > 1 or build_threaded

@jayeshkrishna
Copy link
Contributor Author

@jgfouca : Is this the right fix?

@jgfouca
Copy link
Contributor

jgfouca commented Mar 9, 2017

@jayeshkrishna , yes, putting it in now.

@rljacob
Copy link
Member

rljacob commented Mar 9, 2017

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.

@ghost ghost assigned jgfouca Mar 9, 2017
@ghost ghost added the in progress label Mar 9, 2017
@ekluzek
Copy link
Contributor

ekluzek commented Mar 9, 2017

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! ;-)

@rljacob
Copy link
Member

rljacob commented Mar 9, 2017

The comment for that message says:

# special case for clm
# clm 4_0 is not a shared library and must be built here
# clm 4_5 and newer is a shared library (but not in ACME) and should be built in build_libraries

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?

@jedwards4b
Copy link
Contributor

It's shared by multiple tests.

jgfouca added a commit that referenced this issue Mar 10, 2017
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
@ghost ghost removed the in progress label Mar 10, 2017
agsalin pushed a commit that referenced this issue Mar 29, 2017
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]
jgfouca pushed a commit that referenced this issue Feb 23, 2018
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]
jgfouca pushed a commit that referenced this issue Mar 13, 2018
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]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants