Skip cosmo5.01_fresh and CLM3.5 during recursive submodule clone - #136
Conversation
|
|
|
Actually I am still running old testcases for backward compatibility with
However, as I understand, this will still be possible with the explicit commands and that is completely fine with me to restrict the general command to TSMP2 component models. |
|
However, I think this problem with the CLM3.5-ParFlow-PDAF build should be resolved before merging: https://github.com/HPSCTerrSys/TSMP2/actions/runs/30379409691/job/90343260280 seems the |
|
I see that the CI should be fine before merging. I will take a look. |
|
I just investigated a little more into it and I think that is not enough to overried the From the manpage:
|
models/cosmo5.01_freshpoints to a repository that require authentication. Because of that,git clone --recurse-submodulesandgit submodule update --init --recursivefail (or hang waiting for password) for anyone who doesn't have credentials for this mirror, even if they don't need this component.I would suggest that in this case the TSMP1 components (COSMO and CLM3.5) are not cloned to avoid confusion.
If one specifically need cosmo5.01_fresh or CLM3.5, one can still clone these repositories:
git submodule update --init models/cosmo5.01_fresh
or
git submodule update --init models/CLM3.5