Update versions of ECMWF libraries - #2051
Conversation
|
@fmahebert What's the status of this PR? |
|
Waiting for reviews, I would say |
There are CI failures (e.g. https://github.com/JCSDA/spack-stack/actions/runs/28553787029/job/84656676119?pr=2051) because we don't have the upstream changes in our fork of spack-packages yet. I don't remember what we discussed - who was supposed to do the cherry-picking? |
|
If my memory is correct, I'd discussed this with @eap in June and he'd indicated he'd take over the cherry-picking once the upstream was in. Evan, is this still something you can do? Or should we re-assign? |
I can do that real quick. We have a number of updates in spack-packages for which we need a submodule pointer in spack-stack anyway. |
|
@fmahebert Can you please pull in develop in your spack-stack branch, and then point the spack-packages submodule ( |
|
@fmahebert I pushed an update to your branch that points See 253c095 |
cb2f00c to
f734aeb
Compare
|
Thanks Dom for hooking the PRs together. After some manual testing, I think I understand the CI failure:
So we have two options,
I'm leaning towards (1), because as far as I know the partners using spack-stack don't rely on odc, so a minor version bump in odc shouldn't be disruptive. Do you have an opinion on the matter @climbfuji ? |
That said, a minor version bump is likely fine. |
I was not aware, @rickgrubin-noaa, so thanks for filling me in! If you and Dom agree, I will put in a PR for odc 1.6.3 in spack-packages so we can bring it in here. |
Description
Update ECMWF libraries used by JEDI:
Dependencies
Issues addressed
Closes #2037
Applications affected
JEDI
Systems affected
Testing
Checklist