Revert "Update scorpio"#360
Merged
xylar merged 1 commit intoE3SM-Project:developfrom Mar 18, 2026
Merged
Conversation
This reverts commit dfcffe1.
Author
|
This is required before #361 to avoid conflicts and to keep things clear. |
6 tasks
Author
TestingTested together with #361. See #361 (comment). |
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This reverts commit dfcffe1.
We should not have updated an external submodule directly in Omega in #325 (my mistake!). Instead, we need to bring in changes like this scorpio update via merging
E3SM/masterintoOmega/develop. I will follow up immediately with such a merge.Checklist
Testingwith the following:have been run on and indicate that are all passing.
has passed, using the Polaris
e3sm_submodules/Omegabaseline-pfor both the baseline (Polarise3sm_submodules/Omega) and the PR build