-
Notifications
You must be signed in to change notification settings - Fork 901
WeeklyTelcon_next
Jeff Squyres edited this page May 21, 2024
·
30 revisions
- Dialup Info: (Do not post to public mailing list or public wiki)
- TBA
- v4.1.x Issues; v4.1.x Questions
- v4.1.x Open PRs
- Next release end of Q1. Jeff and Brian will take it on a as-needed basis.
- New issues since v5.0.3
- Open PRs since v5.0.3
- Closed/Merged PRs since v5.0.3
- v5.0.x Open PRs
- v5.0.x Issues; v5.0.x Questions
- PRTE issue if PMIx upgrades from v4.x to v5.x without also rebuilding PRTE
- PMIx changed some internal data structures between v4.x and v5.x (specifically, they are not part of the PMIx public API).
- The PMIx public API did not change between v4.x and v5.x, so the libpmix .so number did not change to reflect an incompatibility.
- PRTE uses the internal PMIx data structures, however, and is affected by the changes between PMIx v4.x and v5.x.
- Meaning: if you build+install PRTE against PMIx v4.x and then upgrade to PMIx v5.x without also re-building PRTE, PRTE will almost certainly segv.
- Since PRTE is the back-end of mpirun, this affects Open MPI as well.
- Upstream PRTE is likely to put in a run-time check to print an error and abort (before segv'ing) when detecting this case.
- https://github.com/openpmix/prrte/pull/1982
- Now we have our own PRRTE. People should watch out for pull requests https://github.com/open-mpi/prrte/pulls
- Need to discuss MPI 4.1
- Need to discuss MPI 4.0
- Discuss set v5.0.4 timeline
- Discuss v6.0 feature list and timeline
- Discuss 6.0: BigCount
- Explore cherry-pick bots
- Explore an MTT alternative