[hwloc-devel] Create success (hwloc r1.7.2rc1r5685)

Creating nightly hwloc snapshot SVN tarball was a success. Snapshot: hwloc 1.7.2rc1r5685 Start time: Wed Jun 19 21:05:08 EDT 2013 End time: Wed Jun 19 21:09:00 EDT 2013 Your friendly daemon, Cyrador

[hwloc-devel] Create success (hwloc r1.8a1r5687)

Creating nightly hwloc snapshot SVN tarball was a success. Snapshot: hwloc 1.8a1r5687 Start time: Wed Jun 19 21:01:01 EDT 2013 End time: Wed Jun 19 21:05:08 EDT 2013 Your friendly daemon, Cyrador

Re: [OMPI devel] BTL sendi

Then let me provide a more elaborate answer. In the original design of the btl_sendi operation we do not provide an upper limit for the sendi (in the same sense as the eager protocol). Thus, an upper layer (PML in this instance) cannot know if the sendi will succeed or not before the call

Re: [OMPI devel] two questions about 1.7.1

On Jun 19, 2013, at 9:26 AM, "Jeff Squyres (jsquyres)" wrote: > How did you configure/compile Open MPI? Paul replied with his configure line off-list; I see the issue. The printf is in an example MPI extension that is not meant to be compiled into a production build of

Re: [OMPI devel] two questions about 1.7.1

On Jun 19, 2013, at 7:52 AM, Paul Kapinos wrote: > Hello All, > > I. > Using the new Open MPI 1.7.1 we see some messages on the console: > > > example mpiext init > > example mpiext fini > > ... on each call to MPI_INIT, MPI_FINALIZE at least in Fortran programs. >

[OMPI devel] End of life: original hg mirror on www.open-mpi.org

Per http://www.open-mpi.org/svn/mercurial.php, we have a deprecated hg mirror running on www.open-mpi.org. We moved the hg mirror out to bitbucket quite a while ago (https://bitbucket.org/ompiteam/ompi-svn-mirror/overview); it's been quite stable out there. IU just asked me if they can shut

[OMPI devel] two questions about 1.7.1

Hello All, I. Using the new Open MPI 1.7.1 we see some messages on the console: > example mpiext init > example mpiext fini ... on each call to MPI_INIT, MPI_FINALIZE at least in Fortran programs. Seems somebody forgot to disable some 'printf'-debug-output? =) II. In the 1.7.x series, the