Release of PMIx v5.0.11 and PRRTE v3.0.14

3 views
Skip to first unread message

Ralph Castain

unread,
Jun 23, 2026, 1:42:14 PMJun 23
to pm...@googlegroups.com
Hello folks

Couple of critical things showed up in the earlier release branches, so we are releasing a (hopefully) final update to them.

-----------------

IMPORTANT
This release contains the following important changes:

  • restoration/repair of the OmniPath support component
  • Repair support of OMPI default MCA params

Detailed changes include:

  • PR #3869: Multiple commits
    • Update NEWS and VERSION
    • pmdl/ompi: use the right type to enumerate myenvars
    • fix var group lookup in component repository release
    • Prepend I/O residuals to correct redirected streams
    • Restore pnet/opa component
    • Don't pass zero-byte stdin to host
    • Correct the wrapper compiler man page
    • Default output to file to nocopy
    • Properly handle qualified values in client get
    • Do not double-process IOF formats
    • Correct cflags used for check_compiler_version.m4
    • Fully support return of static values


---------------------

IMPORTANT
This release contains the following important changes:

  • repair of support for STOP-ON-EXEC debugger operations.
    The ptrace usage must be pinned to the correct thread
    and the wait-for-child-exit logic updated to deal with
    stop/wakeup of the process
  • repair of the LSF mapper when LSB_AFFINITY_HOSTFILE is
    set but empty. Mapper must fallback to a different method.

Detailed changes include:

  • PR #24: Update NEWS and VERSION for release
  • PR #2477: Multiple commits
    • odls: fix STOP_ON_EXEC race between do_parent and wait_signal_callback
    • examples/debugger: add STOP_ON_EXEC support to indirect + daemon
    • odls: pin STOP_ON_EXEC children to prte_event_base (ptrace tracer-thread affinity)
  • PR #2476: Multiple commits
    • fix: rmaps/lsf mapper broken when LSB_AFFINITY_HOSTFILE is set but empty
    • fix: suppress unused-parameter warning in prte_hide_unused_params

Reply all
Reply to author
Forward
0 new messages