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

manage_externals broken in noresm2_3_develop #556

Open
gold2718 opened this issue Sep 6, 2024 · 5 comments
Open

manage_externals broken in noresm2_3_develop #556

gold2718 opened this issue Sep 6, 2024 · 5 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@gold2718
Copy link

gold2718 commented Sep 6, 2024

After running ./manage_externals/checkout_externals on the noresm2_3_develop branch, rerunning the command fails due to a bad status check (running ./manage_externals/checkout_externals --status shows the same bad status):

 M  ./components/blom

To Reproduce
Steps to reproduce the behavior:

  1. Checkout noresm2_3_develop: (git checkout <origin>/noresm2_3_develop)
  2. Run manage_externals: (./manage_externals/checkout_externals)
  3. Attempt to run manage_externals again (./manage_externals/checkout_externals)

Expected behavior
The second run should complete with no errors and no actions.

@gold2718 gold2718 added the bug Something isn't working label Sep 6, 2024
@gold2718 gold2718 added this to the NorESM2.3 milestone Sep 6, 2024
@gold2718 gold2718 self-assigned this Sep 6, 2024
@TomasTorsvik
Copy link
Contributor

The problem is apparently caused by the M4AGO-sinking-scheme submodule

In the blom component

diff --git a/pkgs/M4AGO-sinking-scheme b/pkgs/M4AGO-sinking-scheme
index 99db47f..82568db 160000
--- a/pkgs/M4AGO-sinking-scheme
+++ b/pkgs/M4AGO-sinking-scheme
@@ -1 +1 @@
-Subproject commit 99db47ff6328eb7e006257ae0bc9ed5cc588f711
+Subproject commit 82568dbe4ee402804894020ccf602cff0d0a251e

@gold2718
Copy link
Author

gold2718 commented Sep 7, 2024

The problem is apparently caused by the M4AGO-sinking-scheme submodule

Yes, this is the reason manage_externals reports a modification. However, because that modification was created by manage_externals (because the Externals_BLOM.cfg file overrides the committed submodule hash), I think it should understand that and not report a modification.

@jmaerz
Copy link
Contributor

jmaerz commented Sep 9, 2024

Dear @gold2718 and @TomasTorsvik , just in case: I can tag the 99db47ff... M4AGO commit, so that it becomes easier to handle this, if needed (and/or update the commit in BLOM to the most recent version).

@TomasTorsvik
Copy link
Contributor

@jmaerz - thanks, that should solve the immediate problem.

@jmaerz
Copy link
Contributor

jmaerz commented Sep 9, 2024

Hi @TomasTorsvik , I just pushed tag dev-1.0.1 which is equivalent to sha 99db47ff632, so you can change the BLOM_externals.cfg file for the new tag - which hopefully resolves the immediate issue - while I am not sure, if it should be the default behavior of cime to cause issues when checking out the externals transmitted through a component externals file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Todo
Development

No branches or pull requests

4 participants