Skip to content

Restrict UCX transports in CI to work around mpich 5 default - #186

Merged
xylar merged 1 commit into
MPAS-Dev:mainfrom
xylar:fix-mpich-ci
Aug 1, 2026
Merged

Restrict UCX transports in CI to work around mpich 5 default#186
xylar merged 1 commit into
MPAS-Dev:mainfrom
xylar:fix-mpich-ci

Conversation

@xylar

@xylar xylar commented Aug 1, 2026

Copy link
Copy Markdown
Collaborator

Without this, CI is failing.

mpich 5 is built as ch4:ucx,ofi in conda-forge, making UCX the default
netmod (4.x was ofi-only).  Every MPI_Init() now goes through UCX,
including the one inside ESMF_RegridWeightGen for serial, single-rank
mapping-file generation.

On Azure-hosted GitHub runners, UCX enumerates the MANA adapter and
fails to open an RDMA verbs interface on it:

    UCX ERROR uct_iface_open(ud_verbs/mana_0:1) failed: Address not valid
    MPIDI_UCX_init_worker(86): ucx function returned with failed status
    MPI_Init(argc=(nil), argv=(nil)) failed

ESMF_RegridWeightGen then aborts with exit 143, failing all the
remapping tests.  Runners without a verbs device are unaffected, which
is why this does not reproduce on typical development machines.

Set UCX_TLS at the workflow level so it covers both the test job and the
rattler-build package job.  This is deliberately not set in pixi.toml's
activation, since forcing IB traffic over TCP would hurt real parallel
regridding with mapParallelExec on HPC machines.
@xylar xylar self-assigned this Aug 1, 2026
@xylar xylar added ci Changes that affect github actions CI bug Something isn't working labels Aug 1, 2026
@xylar
xylar merged commit afe915a into MPAS-Dev:main Aug 1, 2026
6 checks passed
@xylar
xylar deleted the fix-mpich-ci branch August 1, 2026 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working ci Changes that affect github actions CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant