FYI - v3.0.0 will go into master for the OMPI v4 branch. v2.1.2 should go into updates for OMPI v3.1 and v3.0 branches
Ralph > Begin forwarded message: > > From: "r...@open-mpi.org" <r...@open-mpi.org> > Subject: [pmix] Release candidates available for testing > Date: June 29, 2018 at 8:54:01 AM PDT > To: pmix <p...@googlegroups.com> > Reply-To: p...@googlegroups.com > > Hello folks > > Release candidates for v2.1.2 and v3.0.0 have been posted: > https://github.com/pmix/pmix/releases/ > <https://github.com/pmix/pmix/releases/> > > Please test them! > Ralph > > v3.0.0 > ---------------------------------------------------------- > This is the start of a new release series based on the PMIx v3 standard. > > **** NOTE: This release implements the complete PMIX v3.0 Standard > **** and therefore includes a number of new APIs and features. These > **** can be tracked by their RFC's on the community website: > **** https://pmix.org/pmix-standard <https://pmix.org/pmix-standard>. > > • Added blocking forms of several existing APIs: > • PMIx_Log > • PMIx_Allocation_request > • PMIx_Job_control > • PMIx_Process_monitor > • Added support for getting/validating security credentials > • PMIx_Get_credential, PMIx_Validate_credential > • Extended support for debuggers/tools > • Added IO forwarding support allowing tools to request > forwarding of output from specific application procs, > and to forward their input to specified target procs > • Extended tool attributes to support synchronization > during startup of applications. This includes the > ability to modify an application's environment > (including support for LD_PRELOAD) and define an > alternate fork/exec agent > • Added ability for a tool to switch server connections > so it can first connect to a system-level server to > launch a starter program, and then reconnect to that > starter for debugging purposes > • Extended network support to collect network inventory by > either rolling it up from individual nodes or by direct > query of fabric managers. Added an API by which the > host can inject any rolled up inventory into the local > PMIx server. Applications and/or the host RM can access > the inventory via the PMIx_Query function. > • Added the ability for applications and/or tools to register > files and directories for cleanup upon their termination > • Added support for inter-library coordination within a process > • Extended PMIx_Log support by adding plugin support for new > channels, including local/remote syslog and email. Added > attributes to query available channels and to tag and > format output. > • Fix several memory and file descriptor leaks > > > > v2.1.2 > -------------------------------------------------------- > This is a bug fix release in the v2.1 series: > > • Added PMIX_VERSION_RELEASE string to pmix_version.h > • Added PMIX_SPAWNED and PMIX_PARENT_ID keys to all procs > started via PMIx_Spawn > • Fixed faulty compares in PMI/PMI2 tests > • Fixed bug in direct modex for data on remote node > • Correctly transfer all cached job info to the client's > shared memory region upon first connection > • Fix potential deadlock in PMIx_server_init in an error case > • Fix uninitialized variable > • Fix several memory and file descriptor leaks > > > -- > You received this message because you are subscribed to the Google Groups > "pmix" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pmix+unsubscr...@googlegroups.com > <mailto:pmix+unsubscr...@googlegroups.com>. > To post to this group, send email to p...@googlegroups.com > <mailto:p...@googlegroups.com>. > Visit this group at https://groups.google.com/group/pmix > <https://groups.google.com/group/pmix>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/pmix/94222748-5185-442F-8CDA-45CABE5E14A5%40open-mpi.org > > <https://groups.google.com/d/msgid/pmix/94222748-5185-442F-8CDA-45CABE5E14A5%40open-mpi.org?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>.
_______________________________________________ devel mailing list email@example.com https://lists.open-mpi.org/mailman/listinfo/devel