Update ursa to oneapi@2025.3.1 compilers and mpi@2021.17 MPI

[rickgrubin-noaa]

Description

Update ursa to oneapi@2025.3.1 compilers and mpi@2021.17 MPI.

HPC-X MPI remains at v2.18.1

Dependencies

None

Issues addressed

None

Applications affected

All applications that build against spack-stack (UFS WM, SRW, etc.)

Systems affected

ursa

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)

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]

Is this for the release/2.1 branch?

[climbfuji]

No problem adding this, but surprised that it is necessary

[rickgrubin-noaa]

No problem adding this, but surprised that it is necessary

Unclear if it's strictly necessary; I simply didn't remove it from 2025.2.1 config yaml files.

[climbfuji]

Both of these are missing the compiler requirement sections. From Atlantis:

  all:
    require:
    - any_of: ['%intel-oneapi-compilers@=2025.3.0']
      when: '%intel-oneapi-compilers'
    - any_of: ['%gcc@=11.2.0']
      when: '%gcc'

[rickgrubin-noaa]

Is this for the release/2.1 branch?

I submitted against develop; can close this PR and submit against release/2.1 if you prefer.

[rickgrubin-noaa]

Both of these are missing the compiler requirement sections. From Atlantis:

  all:
    require:
    - any_of: ['%intel-oneapi-compilers@=2025.3.0']
      when: '%intel-oneapi-compilers'
    - any_of: ['%gcc@=11.2.0']
      when: '%gcc'

Thanks, wasn't aware of this, and will update accordingly.

[climbfuji]

Is this for the release/2.1 branch?

I submitted against develop; can close this PR and submit against release/2.1 if you prefer.

Yes please, and while at it you may commit the changes with [skip ci] in the last commit message to prevent the CI tests from running for site config changes.

I tried to change the base for this PR to release/2.1, but that would bring in the ESMF changes from develop that we don't want in the release branch.

Sorry for the hassle!

[rickgrubin-noaa]

Is this for the release/2.1 branch?

I submitted against develop; can close this PR and submit against release/2.1 if you prefer.

Yes please, and while at it you may commit the changes with [skip ci] in the last commit message to prevent the CI tests from running for site config changes.

I tried to change the base for this PR to release/2.1, but that would bring in the ESMF changes from develop that we don't want in the release branch.

Sorry for the hassle!

Not a problem; will get it gone today.

[rickgrubin-noaa]

Closing per discussion herein, will re-open against release/2.1