Re: [OMPI devel] Github deprecated "Github services" Does this affect us?

2018-06-08 Thread Jeff Squyres (jsquyres) via devel
The only thing it affects that we were using was Travis. But a) we're no longer using Travis, and b) I'm sure Travis will address the issue, anyway. > On Jun 7, 2018, at 10:06 AM, Geoffrey Paulsen wrote: > > Devel, > >I just came across Github's deprecation announcement of Github

Re: [OMPI devel] Shared object dependencies

2018-06-08 Thread Jeff Squyres (jsquyres) via devel
Before digging any deeper, did you perchance install multiple versions of Open MPI into the same prefix? If so, remember that Open MPI installs lots of plugins. The exact set of plugins changes every release. So if you install version A.B.C in to /opt/openmpi, and then install version X.Y.Z

Re: [OMPI devel] openmpi-3.1.0 cygwin patch

2018-06-16 Thread Jeff Squyres (jsquyres) via devel
Thanks Macro. I've filed https://github.com/open-mpi/ompi/pull/5277 here for master; will follow up with PR's to the release branches after that passes CI / is merged. > On Jun 11, 2018, at 10:43 AM, Marco Atzeri wrote: > > On 5/28/2018 11:58 AM, Marco Atzeri wrote: >> On 5/24/2018 11:07

Re: [OMPI devel] Shared object dependencies

2018-06-12 Thread Jeff Squyres (jsquyres) via devel
On Jun 12, 2018, at 7:21 AM, Gilles Gouaillardet wrote: > > I think this also depends on the linker (configuration ?) and possibly the > order the libraries are dlopen’ed. > > Note the issue was initially reported (as warnings only) from ompi_info, so > there is a possibility it we all

Re: [OMPI devel] Shared object dependencies

2018-06-12 Thread Jeff Squyres (jsquyres) via devel
How is it that Edgar is not running into these issues? Edgar: are you compiling with --disable-dlopen, perchance? > On Jun 12, 2018, at 6:04 AM, Gilles Gouaillardet > wrote: > > Edgar, > > Regarding this specific problem, the issue is mca_fcoll_individual.so did not > depend on

Re: [OMPI devel] Shared object dependencies

2018-06-12 Thread Jeff Squyres (jsquyres) via devel
On Jun 12, 2018, at 7:34 AM, Gabriel, Edgar wrote: > > Well, I am still confused. What is different on nixOS vs. other linux distros > that makes this error appear, Fair enough. I don't think I realized nixOS was a Linux distro. That being said, every time I think I understand linkers, I

[OMPI devel] Removing the oob/ud component

2018-06-19 Thread Jeff Squyres (jsquyres) via devel
We talked about this on the webex today, but for those of you who weren't there: we're talking about removing the oob/ud component: https://github.com/open-mpi/ompi/pull/5300 We couldn't find anyone who still cares about this component (e.g., LANL, Mellanox, ...etc.), and no one is

Re: [OMPI devel] Removing the oob/ud component

2018-06-19 Thread Jeff Squyres (jsquyres) via devel
se instead? I’m pretty sure oob/ud is > being picked by default on our IB cluster. Or is oob/tcp good enough? > > Cheers, > Ben > >> On 20 Jun 2018, at 5:20 am, Jeff Squyres (jsquyres) via devel >> wrote: >> >> We talked about this on the webex today, but

Re: [OMPI devel] Master broken

2018-06-04 Thread Jeff Squyres (jsquyres) via devel
Fix should now be merged. > On Jun 4, 2018, at 1:20 PM, Peter Kjellström wrote: > > On Sun, 3 Jun 2018 08:41:42 -0700 > Thananon Patinyasakdikul wrote: > >> It is tested against 1.5. it should not work with lower version. I >> will fix it. > > FWIW, it also builds ok against up to date

Re: [OMPI devel] Remove prun tool from OMPI?

2018-06-05 Thread Jeff Squyres (jsquyres) via devel
No objection from me. > On Jun 5, 2018, at 12:09 PM, r...@open-mpi.org wrote: > > Hey folks > > Does anyone have heartburn if I remove the “prun” tool from ORTE? I don’t > believe anyone is using it, and it doesn’t look like it even works. > > I ask because the name conflicts with PRRTE and

Re: [OMPI devel] Open MPI: Undefined reference to pthread_atfork

2018-06-22 Thread Jeff Squyres (jsquyres) via devel
On Jun 22, 2018, at 4:09 PM, lille stor wrote: > > I tried compile the C++ program using "mpic++" like you suggested but > unfortunately g++ still throws the same errror > ("/home/dummy/openmpi/build/lib/libopen-pal.so.20: undefined reference to > pthread_atfork"). > > I suspect that the

Re: [OMPI devel] Open MPI: Undefined reference to pthread_atfork

2018-06-22 Thread Jeff Squyres (jsquyres) via devel
Can you send all the information listed here: https://www.open-mpi.org/community/help/ > On Jun 22, 2018, at 4:44 PM, lille stor wrote: > > Thanks again Jeff. > > Here is the output of running "mpic++" with parameter "--showme" (in bold > what "mpic++" added): > > g++ test.cpp

Re: [OMPI devel] Open MPI: Undefined reference to pthread_atfork

2018-06-22 Thread Jeff Squyres (jsquyres) via devel
I think Ralph is a little confused -- 2.1.3 is recent enough. :-) Are you using "mpic++" to compile your application? That should add in all the relevant flags that are needed to compile an Open MPI C++ application. > On Jun 22, 2018, at 3:29 PM, r...@open-mpi.org wrote: > > OMPI 2.1.3???

Re: [OMPI devel] New binding option

2018-06-21 Thread Jeff Squyres (jsquyres) via devel
On Jun 21, 2018, at 9:41 AM, r...@open-mpi.org wrote: > > Alternatively, processes can be assigned to processors based on > their local rank on a node using the \fI--bind-to cpuset:ordered\fP option > with an associated \fI--cpu-list "0,2,5"\fP. This directs that the first > rank on a node be

Re: [OMPI devel] New binding option

2018-06-21 Thread Jeff Squyres (jsquyres) via devel
On Jun 21, 2018, at 10:26 AM, r...@open-mpi.org wrote: > >>> Alternatively, processes can be assigned to processors based on >>> their local rank on a node using the \fI--bind-to cpuset:ordered\fP option >>> with an associated \fI--cpu-list "0,2,5"\fP. This directs that the first >>> rank on a

Re: [OMPI devel] Continued warnings?

2018-07-31 Thread Jeff Squyres (jsquyres) via devel
Confirmed and filed https://github.com/open-mpi/ompi/issues/5502. > On Jul 31, 2018, at 9:31 AM, Ralph H Castain wrote: > > Just curious - will this ever be fixed? From today’s head of master: > > In file included from info.c:46:0: > info.c: In function 'opal_info_dup_mode': >

Re: [OMPI devel] Open MPI v2.1.4rc1

2018-08-10 Thread Jeff Squyres (jsquyres) via devel
ccs-svm1_home1/gvh/.ompi-release-tester/scratch/summitdev/2.1.4rc1/scratch/UCX/ompi_build/ompi' > make: *** [all-recursive] Error 1 > > My 2 cents, > >> On Aug 6, 2018, at 5:04 PM, Jeff Squyres (jsquyres) via devel >> wrote: >> >> Open MPI v2.1.4rc1 has been

[OMPI devel] Open MPI v2.1.4rc1

2018-08-06 Thread Jeff Squyres (jsquyres) via devel
Open MPI v2.1.4rc1 has been pushed. It is likely going to be the last in the v2.1.x series (since v4.0.0 is now visible on the horizon). It is just a bunch of bug fixes that have accumulated since v2.1.3; nothing huge. We'll encourage users who are still using the v2.1.x series to upgrade to

[OMPI devel] v2.1.5rc1 is out

2018-08-15 Thread Jeff Squyres (jsquyres) via devel
Per our discussion over the weekend and on the weekly webex yesterday, we're releasing v2.1.5. There are only two changes: 1. A trivial link issue for UCX. 2. A fix for the vader BTL issue. This is how I described it in NEWS: - A subtle race condition bug was discovered in the "vader" BTL

[OMPI devel] Next Open MPI face-to-face meeting

2018-08-14 Thread Jeff Squyres (jsquyres) via devel
It's been settled: 9am Tue, Oct 16 - noonish Thu Oct 18 At Cisco, San Jose, CA, USA Put your name on the wiki if you're going to attend (so that I can get guest badge+wifi for you): https://github.com/open-mpi/ompi/wiki/Meeting-2018-09 Start adding agenda items. -- Jeff Squyres

[OMPI devel] lists.open-mpi.org appears to be back

2018-08-28 Thread Jeff Squyres (jsquyres) via devel
The lists.open-mpi.org server went offline due to an outage at our hosting provider sometime in the evening on Aug 22 / early morning Aug 23 (US Eastern time). The list server now appears to be back online; I've seen at least a few backlogged emails finally come through. If you sent a mail in

[OMPI devel] Test mail

2018-08-28 Thread Jeff Squyres (jsquyres) via devel
Will this get through? -- Jeff Squyres jsquy...@cisco.com ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel

[OMPI devel] lists.open-mpi.org appears to be back

2018-08-28 Thread Jeff Squyres (jsquyres) via devel
The lists.open-mpi.org server went offline due to an outage at our hosting provider sometime in the evening on Aug 22 / early morning Aug 23 (US Eastern time). As of yesterday morning (Saturday, Aug 25), the list server now appears to be back online; I've seen at least a few backlogged emails

Re: [OMPI devel] lists.open-mpi.org appears to be back

2018-08-28 Thread Jeff Squyres (jsquyres) via devel
I originally sent this mail on Saturday, but it looks like lists.open-mpi.org was *not* actually back at this time. I'm finally starting to see all the backlogged messages on Tuesday, around 5pm US Eastern time. So I think lists.open-mpi.org is finally back in service. Sorry for the

Re: [OMPI devel] v2.1.5rc1 is out

2018-08-17 Thread Jeff Squyres (jsquyres) via devel
>> 7 0x000a2488 PMPI_Win_create() ??:0 >> 8 0x1000b28c IMB_window() ??:0 >> 9 0x10005764 IMB_init_buffers_iter() ??:0 >> 10 0x10001ef8 main() ??:0 >> 11 0x000000024980 generic_start_main.isra.0() libc-start.c:0 >> 12

Re: [OMPI devel] openmpi 3.1.x examples

2018-07-17 Thread Jeff Squyres (jsquyres) via devel
On Jul 17, 2018, at 1:18 AM, Marco Atzeri wrote: > > I was aware, as I am not building it anymore, however > probably we should exclude the C++ from default examples. examples/Makefile won't build the C++ (or Fortran or OSHMEM) examples if they aren't built. My $0.02: As long as we're

Re: [OMPI devel] [p]ompi_foo_f symbols in mpi_f08.mod

2018-07-17 Thread Jeff Squyres (jsquyres) via devel
On Jul 17, 2018, at 8:49 PM, Gilles Gouaillardet wrote: > > I noted the internal Fortran bindings (e.g. [p]ompi_barrier_f and friends) > are defined in the user facing mpi_f08.mod. > > My impressions are : > > 1. pompi_barrier_f and friends are never used (e.g. pbarrier_f08.F90 calls >

[OMPI devel] v4.0.x -> v5.0.x: .so versioning, etc.

2018-07-18 Thread Jeff Squyres (jsquyres) via devel
Devel community: We had a lengthy discussion on the weekly webex yesterday about a request from our downstream packagers: if possible, they would strongly prefer if we did not change the major .so version in the upcoming v4.0.x. The exact rationale for this gets quite complex, but the short

[OMPI devel] Cygwin Fortran compiler options (was: openmpi 3.1.x examples)

2018-07-16 Thread Jeff Squyres (jsquyres) via devel
Split the Fortran issue off into its own thread (and kept it on devel; no need for ompi-packagers) On Jul 13, 2018, at 4:35 PM, Marco Atzeri wrote: > > the fortran problem is due to a compiler settings > It works with > > $ mpifort -g hello_usempi.f90 -o hello_usempi

Re: [OMPI devel] openmpi 3.1.x examples

2018-07-16 Thread Jeff Squyres (jsquyres) via devel
On Jul 13, 2018, at 4:35 PM, Marco Atzeri wrote: > >> For one. The C++ bindings are no longer part of the standard and they are >> not built by default in v3.1x. They will be removed entirely in Open MPI >> v5.0.0. Hey Marco -- you should probably join our packagers mailing list:

Re: [OMPI devel] Test mail

2018-09-01 Thread Jeff Squyres (jsquyres) via devel
Heh. That was a backlog email that was delivered quite a ways after it was actually sent. Safe to ignore this thread. > On Aug 28, 2018, at 6:34 PM, Nathan Hjelm wrote: > > no > > Sent from my iPhone > >> On Aug 27, 2018, at 8:51 AM, Jeff Squyres (jsquyr

Re: [OMPI devel] Open MPI website borked up?

2018-09-04 Thread Jeff Squyres (jsquyres) via devel
Yes, there was a problem for a short while last week; it was fixed. > On Sep 1, 2018, at 4:55 PM, Ralph H Castain wrote: > > I suspect this is a stale message - I’m not seeing any problem with the > website > > >> On Aug 29, 2018, at 12:55 PM, Howard Pritchard wrote: >> >> Hi Folks, >>

Re: [OMPI devel] Will info keys ever be fixed?

2018-09-11 Thread Jeff Squyres (jsquyres) via devel
Ralph -- What OS / compiler are you using? I just compiled on MacOS (first time in a while) and filed a PR and a few issues about the warnings I found, but I cannot replicate these warnings. I also built with gcc 7.3.0 on RHEL; couldn't replicate the warnings. On MacOS, I'm using the default

Re: [OMPI devel] Cannot find libverbs when without-verbs is used

2018-09-11 Thread Jeff Squyres (jsquyres) via devel
I notice from your configure log that you're building Mellanox MXM support. Does that pull in libibverbs as a dependent library? > On Sep 11, 2018, at 7:23 AM, Mijakovic, Robert > wrote: > > Hi guys, > > I have configured OpenMPI to build without-verbs but the build fails with an > error

Re: [OMPI devel] Openmpi configure: Could not determine the fortran compiler flag

2018-10-22 Thread Jeff Squyres (jsquyres) via devel
error produced). > > PS: To try moving further, I did > ./configure --prefix=$HOME/usr/local --disable-mpi-fortran > which led me to a later error. This is posted in a separate thread. > > > On Sun, Oct 21, 2018 at 2:25 PM Jeff Squyres (jsquyres) via devel > wrote: >

Re: [OMPI devel] Openmpi configure: Could not determine the fortran compiler flag

2018-10-22 Thread Jeff Squyres (jsquyres) via devel
> On Oct 22, 2018, at 12:58 PM, Santiago Serebrinsky > wrote: > > Precisely, that was the problem. > > I disabled Fortran support to move ahead and see if I could manage that way > (and I found I couldn't!), at least in some of my uses. But I (and perhaps > others as well) would still need

Re: [OMPI devel] Openmpi configure: Could not determine the fortran compiler flag

2018-10-21 Thread Jeff Squyres (jsquyres) via devel
Also, please send the entire output from configure as well as the config.log file (please compress). Thanks! > On Oct 21, 2018, at 4:08 AM, Marco Atzeri wrote: > > Am 21.10.2018 um 09:56 schrieb Santiago Serebrinsky: >> Hi all, >> I am using Msys2 from PortableApps under Win10. More

Re: [OMPI devel] Patcher on MacOS

2018-09-28 Thread Jeff Squyres (jsquyres) via devel
I asked a similar question recently: https://github.com/open-mpi/ompi/issues/5671 > On Sep 28, 2018, at 5:21 PM, Barrett, Brian via devel > wrote: > > Is there any practical reason to have the memory patcher component enabled > for MacOS? As far as I know, we don’t have any transports

Re: [OMPI devel] Patcher on MacOS

2018-09-28 Thread Jeff Squyres (jsquyres) via devel
I didn't start working on a patch -- all I did was open #5671. > On Sep 28, 2018, at 5:51 PM, Nathan Hjelm via devel > wrote: > > Nope. We just never bothered to disable it on osx. I think Jeff was working > on a patch. > > -Nathan > >> On Sep 28, 2018, at 3:21 PM, Barrett, Brian via

Re: [OMPI devel] Mac OS X 10.4.x users?

2018-09-28 Thread Jeff Squyres (jsquyres) via devel
Fun fact: we cause configure to fail for OS X <= 10.4 anyway: https://github.com/open-mpi/ompi/blob/master/configure.ac#L328-L347 According to the comment, we do this because of a known-bad implementation of pty in the OS X kernel that causes kernel panics. So I think we're definitely safe

Re: [OMPI devel] btl/vader: race condition in finalize on OS X

2018-10-02 Thread Jeff Squyres (jsquyres) via devel
FYI: https://github.com/open-mpi/ompi/issues/5798 brought up what may be the same issue. > On Oct 2, 2018, at 3:16 AM, Gilles Gouaillardet wrote: > > Folks, > > > When running a simple helloworld program on OS X, we can end up with the > following error message > > > A system call failed

Re: [OMPI devel] Error in TCP BTL??

2018-10-01 Thread Jeff Squyres (jsquyres) via devel
I get that 100% time in the runs on MacOS, too (with today's HEAD): -- $ mpirun -np 4 --mca btl tcp,self ring_c Process 0 sending 10 to 1, tag 201 (4 processes in ring) [JSQUYRES-M-26UT][[5535,1],0][btl_tcp_endpoint.c:742:mca_btl_tcp_endpoint_start_connect] bind() failed: Invalid argument

[OMPI devel] How to know when CI on a PR is done

2018-09-19 Thread Jeff Squyres (jsquyres) via devel
FYI for developers: I just merged a little python script in the ompi-scripts repo that watches for when CI on a PR is done. I find this very handy, especially because Open MPI's CI can take anywhere from 15 minutes to multiple hours. This script lets me file a PR and then move on to something

[OMPI devel] Open MPI SC'18 State of the Union BOF slides

2018-11-16 Thread Jeff Squyres (jsquyres) via devel
Thanks to all who came to the Open MPI SotU BOF at SC'18 in Dallas, TX, USA this week! It was great talking with you all. Here are the slides that we presented: https://www.open-mpi.org/papers/sc-2018/ Please feel free to ask any followup questions on the users or devel lists. -- Jeff

[OMPI devel] Doodle poll for April face-to-face meeting

2019-01-16 Thread Jeff Squyres (jsquyres) via devel
Please don't forget to fill out the Doodle poll to select the week for the next Open MPI developer's face-to-face meeting by COB THIS FRIDAY, JANUARY 18 2019: https://doodle.com/poll/vvvzwuiizy7mnx64 Thanks! -- Jeff Squyres jsquy...@cisco.com

[OMPI devel] For discussion on the Webex tomorrow

2019-01-14 Thread Jeff Squyres (jsquyres) via devel
All -- I'd like to discuss this on the webex tomorrow: https://github.com/open-mpi/ompi/issues/6278 -- Jeff Squyres jsquy...@cisco.com ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel

[OMPI devel] Next Open MPI face-to-face dev meeting

2019-01-15 Thread Jeff Squyres (jsquyres) via devel
Here's a Doodle poll to pick the week of the next face-to-face meeting. We're targeting the April(ish) timeframe: https://doodle.com/poll/vvvzwuiizy7mnx64 Please fill out this doodle by the end of this week (i.e., by COB Friday, 18 Jan 2019). Thank you! -- Jeff Squyres

[OMPI devel] Item for next Tuesday's agenda: remove openib BTL

2019-01-15 Thread Jeff Squyres (jsquyres) via devel
Rats -- I forgot to get this on this morning's webex agenda. Geoff Paulsen -- please add this to next Tuesday's agenda: "Remove openib and affiliated stuff" https://github.com/open-mpi/ompi/pull/6270 -- Jeff Squyres jsquy...@cisco.com ___

[OMPI devel] Location poll for April Open MPI dev face-to-face meeting

2019-01-22 Thread Jeff Squyres (jsquyres) via devel
The week has been chosen: April 22. Now take this poll to register your preference for the location (we're still checking availability, but this at least gets everyone's preferences down): https://docs.google.com/forms/d/e/1FAIpQLSdrJw7xfVNo3nAfoB4dsnMu7ihiZ0WCjglo2KBZqvY_3BZkkg/viewform

Re: [OMPI devel] Help needed debugging openmpi 3.1 builds for Fedora

2018-12-17 Thread Jeff Squyres (jsquyres) via devel
Orion -- Thanks for the bug report; I filed it here: https://github.com/open-mpi/ompi/issues/6200 > On Dec 16, 2018, at 9:55 PM, Orion Poplawski wrote: > > On 12/15/18 1:13 PM, devel@lists.open-mpi.org wrote: >> I'm testing out rebuilding Fedora packages with openmpi 3.1 in Fedora COPR:

[OMPI devel] 2.1.6rc1

2018-11-28 Thread Jeff Squyres (jsquyres) via devel
I just pushed rc1 for what we hope to be the final final final no really trust me final version of the 2.1.x series. We may sit on this release until January, just because everyone is still recovering from SC'18+US Thanksgiving holiday, and we have the MPI Forum next week, and the Christmas

[OMPI devel] Did someone enable Travis?

2019-01-08 Thread Jeff Squyres (jsquyres) via devel
Did someone enable Travis CI on GitHub:open-mpi/ompi? I thought we had specifically disabled Travis after we kept running into problems with it...? I ask because it's failing on some PRs for reasons that seem to have nothing to do with the PR. I don't know if our Travis setup has bit rotted,

Re: [OMPI devel] Did someone enable Travis?

2019-01-08 Thread Jeff Squyres (jsquyres) via devel
It looks like Travis was enabled within the last day or so -- https://travis-ci.org/open-mpi/ompi/pull_requests shows 3 Travis builds on PRs, all submitted within the last 24 hours. The last PR build before that was 2 years ago. I've taken the liberty of re-disabling Travis. Does anyone know

[OMPI devel] Time to remove openib BTL?

2019-01-10 Thread Jeff Squyres (jsquyres) via devel
There's a compile issue in the openib BTL on master - see https://github.com/open-mpi/ompi/issues/6265. It's probably not hard to fix, but... do we care? Is it just time to remove the openib BTL on master? Per https://github.com/open-mpi/ompi/wiki/5.0.x-FeatureList, the openib BTL is on the

Re: [OMPI devel] MTT Perl client

2018-09-14 Thread Jeff Squyres (jsquyres) via devel
It's for environments where MTT is run where it can't reach the greater internet (or, at least, it can't POST to the greater internet). You run the mtt-relay on a machine that is reachable by your machines running MTT, and it works as a relay to mtt.open-mpi.org so that you can submit your MTT

Re: [OMPI devel] MTT Perl client

2018-09-14 Thread Jeff Squyres (jsquyres) via devel
On Sep 14, 2018, at 12:37 PM, Gilles Gouaillardet wrote: > > IIRC mtt-relay is not only a proxy (squid can do that too). Probably true. IIRC, I think mtt-relay was meant to be a dirt-stupid-but-focused-to-just-one-destination relay. > mtt results can be manually copied from a cluster behind

Re: [OMPI devel] Announcing Open MPI v4.0.0rc1

2018-09-18 Thread Jeff Squyres (jsquyres) via devel
On Sep 18, 2018, at 3:46 PM, Thananon Patinyasakdikul wrote: > > I tested on our cluster (UTK). I will give a thumb up but I have some > comments. > > What I understand with 4.0. > - openib btl is disabled by default (can be turned on by mca) It is disabled by default *for InfiniBand*. It

[OMPI devel] New "State" labels in github

2018-09-18 Thread Jeff Squyres (jsquyres) via devel
Brian and I just added some new "State" labels on GitHub to help with managing all the open issues. Please add and keep up to date the "State" labels on your open issues. See this wiki page for more information (might wanna bookmark it):

Re: [OMPI devel] [OMPI commits] Git: open-mpi/ompi branch v4.0.x updated. v1.10.7-1907-g71d3afd

2018-09-11 Thread Jeff Squyres (jsquyres) via devel
On Sep 9, 2018, at 4:29 PM, Gitdub wrote: > > diff --git a/VERSION b/VERSION > index 6fadf03..a9706a3 100644 > --- a/VERSION > +++ b/VERSION > +libmpi_mpifh_so_version=61:0:21 Geoff -- Just curious: any reason this one is 60 and all the others are 61? -- Jeff Squyres jsquy...@cisco.com

Re: [OMPI devel] MTT Perl client

2018-09-11 Thread Jeff Squyres (jsquyres) via devel
Works for me. > On Sep 11, 2018, at 12:35 PM, Ralph H Castain wrote: > > Hi folks > > Per today’s telecon, I have moved the Perl MTT client into its own > repository: https://github.com/open-mpi/mtt-legacy. All the Python client > code has been removed from that repo. > > The original MTT

Re: [OMPI devel] [OMPI commits] Git: open-mpi/ompi branch v4.0.x updated. v1.10.7-1907-g71d3afd

2018-09-11 Thread Jeff Squyres (jsquyres) via devel
On Sep 11, 2018, at 2:17 PM, Jeff Squyres (jsquyres) via devel wrote: > >> diff --git a/VERSION b/VERSION >> index 6fadf03..a9706a3 100644 >> --- a/VERSION >> +++ b/VERSION > >> +libmpi_mpifh_so_version=61:0:21 > > Just curious: any reason this one

[OMPI devel] One-sided tests in MTT

2019-01-30 Thread Jeff Squyres (jsquyres) via devel
Yo Nathan -- I see you just added 2 suites of one-sided tests to the MTT repo. Huzzah! Can you provide some simple recipes -- frankly, for someone who doesn't want/care to know how the tests work :-) -- on how to: 1. Build the test suites 2. Run in MTT Thanks! -- Jeff Squyres

[OMPI devel] MPIX FP16 datatypes

2019-01-31 Thread Jeff Squyres (jsquyres) via devel
All -- Fujitsu has submitted a comprehensive PR to add FP16 datatypes to OMPI under "MPIX_*" names. It adds quite a bit of infrastructure in the datatype and op areas, and then exposes that infrastructure through "MPIX_" names in an mpiext extension. >From a technical standpoint, this PR

[OMPI devel] Open MPI face-to-face

2019-02-07 Thread Jeff Squyres (jsquyres) via devel
It has been settled: Tue Apr 23 - Thu Apr 25, 2019, in San Jose, CA (probably at Cisco). Please add your names and agenda items: https://github.com/open-mpi/ompi/wiki/Meeting-2019-04 -- Jeff Squyres jsquy...@cisco.com ___ devel mailing list

Re: [OMPI devel] One-sided tests in MTT

2019-02-07 Thread Jeff Squyres (jsquyres) via devel
the checks with OMPI_MCA_osc=sm,rdma, > OMPI_MCA_osc=sm,pt2pt, and OMPI_MCA_osc=sm,ucx to test each possible > configuration. > > -Nathan > > On Jan 30, 2019, at 11:26 AM, "Jeff Squyres (jsquyres) via devel" > wrote: > >> Yo Nathan -- >> >> I

[OMPI devel] Queued up Open MPI mails

2019-02-07 Thread Jeff Squyres (jsquyres) via devel
As you can probably tell from the floodgate of backlogged Open MPI mails that probably just landed in your inbox, there was some kind of issue at our mail list provider (but it only affected some of our lists). They just released all the backlogged emails. Enjoy the onslaught! -- Jeff