Skip to content

Update versions of ECMWF libraries - #2051

Open
fmahebert wants to merge 2 commits into
JCSDA:developfrom
fmahebert:feature/new_ecmwf_library_versions
Open

Update versions of ECMWF libraries#2051
fmahebert wants to merge 2 commits into
JCSDA:developfrom
fmahebert:feature/new_ecmwf_library_versions

Conversation

@fmahebert

Copy link
Copy Markdown
Contributor

Description

Update ECMWF libraries used by JEDI:

  • eckit 2.0.7
  • fckit 0.14.3
  • fiat 2.0.0
  • ectrans 1.8.0
  • atlas 0.46.0

Dependencies

Issues addressed

Closes #2037

Applications affected

JEDI

Systems affected

Testing

  • CI: Note whether the automatic tests (GitHub actions tests that run automatically for every commit) pass or not
    • GitHub actions CI tests pass
    • GitHub actions CI tests do not pass (provide explanation)
    • GitHub actions CI tests skipped (provide explanation if necessary)
  • New tests added: List and describe any new tests added to GitHub actions
    • ...
  • Additional testing: Add information on any additional tests conducted
    • Tested jedi-bundle on Ubuntu 24.04 server with these package versions, built with gcc and oneapi, but outside of spack-stack.

Checklist

  • This PR addresses one issue/problem/enhancement or has a very good reason for not doing so.
  • These changes have been tested on the affected systems and applications.
  • All dependency PRs/issues have been resolved and this PR can be merged.
  • All necessary updates to the documentation (spack-stack wiki) will be made when this PR is merged

@climbfuji

Copy link
Copy Markdown
Collaborator

@fmahebert What's the status of this PR?

@fmahebert

Copy link
Copy Markdown
Contributor Author

Waiting for reviews, I would say

@climbfuji

Copy link
Copy Markdown
Collaborator

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?

@fmahebert

Copy link
Copy Markdown
Contributor Author

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?

@climbfuji

Copy link
Copy Markdown
Collaborator

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.

@climbfuji

Copy link
Copy Markdown
Collaborator

@fmahebert Can you please pull in develop in your spack-stack branch, and then point the spack-packages submodule (repos/builtin) to https://github.com/climbfuji/spack-packages/tree/feature/cherrypick_ecmwflibs ? The hash is

commit 2244e6b55ec419dde056737edd39c91001d669c4 (HEAD -> feature/cherrypick_ecmwflibs, dom/feature/cherrypick_ecmwflibs)
Author: Francois Hebert <hebert@ucar.edu>
Date:   Sat Jul 18 22:37:03 2026 -0700

    eckit,cfkit,fiat,ectrans,ecmwf-atlas: Add new versions (#5426)

@climbfuji

climbfuji commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

@fmahebert I pushed an update to your branch that points repos/builtin to JCSDA/spack-packages#75 and pulls in the latest spack-stack develop code.

See 253c095

@climbfuji climbfuji self-assigned this Aug 14, 2026
@climbfuji
climbfuji force-pushed the feature/new_ecmwf_library_versions branch from cb2f00c to f734aeb Compare August 14, 2026 14:49
@fmahebert

Copy link
Copy Markdown
Contributor Author

Thanks Dom for hooking the PRs together.

After some manual testing, I think I understand the CI failure:

  • odc <= 1.6.2 is compatible with eckit 1.x, but doesn't build with eckit 2.x
  • odc 1.6.3 (release early 2026) is compatible with eckit 1.x (at least for recent x) and 2.x

So we have two options,

  1. also include the update from odc 1.6.1 to odc 1.6.3 for spack-stack 2.2
  2. roll back some/all of these ecmwf repo updates

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 ?

@rickgrubin-noaa

Copy link
Copy Markdown
Collaborator

@fmahebert

update from odc 1.6.1 to odc 1.6.3 for spack-stack 2.2

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.

odc is used by NOAA groups that build on top of spack-stack.

That said, a minor version bump is likely fine.

@fmahebert

Copy link
Copy Markdown
Contributor Author

odc is used by NOAA groups that build on top of spack-stack.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update ECMWF libraries

3 participants