release/1.9: Yet another crtm-fix bugfix#546
Merged
climbfuji merged 1 commit intoJCSDA:release/1.9.0from Jun 4, 2025
Merged
Conversation
RatkoVasic-NOAA
approved these changes
Jun 4, 2025
ulmononian
approved these changes
Jun 4, 2025
Collaborator
ulmononian
left a comment
There was a problem hiding this comment.
thanks @climbfuji & @AlexanderRichert-NOAA
Merged
9 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.
Description
Yet another crtm-fix file bugfix for branch release/1.9. This will go into release tag 1.9.2. This and any other of the many crtm-fix bug fixes should be merged back to develop if not yet ...
Submodule pointer update will be handled in JCSDA/spack-stack#1660, but since we've applied this bug fix manually on many platforms, this can be merged anytime.
Also, ignore the Ubuntu 20.04 / Python 3.6 errors, this runner doesn't exist anymore.