Re: [OMPI devel] Master broken

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 libfa

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

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 ca

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

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 Servic

Re: [OMPI devel] Shared object dependencies

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 i

Re: [OMPI devel] Shared object dependencies

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 libmca_commo

Re: [OMPI devel] Shared object dependencies

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 missed

Re: [OMPI devel] Shared object dependencies

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 find

Re: [OMPI devel] openmpi-3.1.0 cygwin patch

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 AM,

[OMPI devel] Removing the oob/ud component

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 maintain

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

uld use 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

Re: [OMPI devel] New binding option

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 boun

Re: [OMPI devel] New binding option

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 nod

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

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??? Is

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

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 pro

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

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 -lUtils

Re: [OMPI devel] openmpi 3.1.x examples

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: https://

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

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 -fintrinsic-modules-pat

Re: [OMPI devel] openmpi 3.1.x examples

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 shipping

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

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_

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

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 ver

Re: [OMPI devel] Continued warnings?

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': > ../../opal/util/

[OMPI devel] Open MPI v2.1.4rc1

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

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

ing directory > `/autofs/nccs-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: >> >

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

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 jsquy...@

[OMPI devel] v2.1.5rc1 is out

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 (s

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

??:0 >> 7 0x000a2488 PMPI_Win_create() ??:0 >> 8 0x1000b28c IMB_window() ??:0 >> 9 0x10005764 IMB_init_buffers_iter() ??:0 >> 10 0x10001ef8 main() ??:0 >> 11 0x00024980 generic_start_main.isra.0() libc-start.c:0 >> 12

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

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] lists.open-mpi.org appears to be back

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 f

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

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 interrupti

[OMPI devel] Test mail

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

Re: [OMPI devel] Test mail

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?

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] Cannot find libverbs when without-verbs is used

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 sa

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

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] [OMPI commits] Git: open-mpi/ompi branch v4.0.x updated. v1.10.7-1907-g71d3afd

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

Re: [OMPI devel] MTT Perl client

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

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

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] MTT Perl client

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

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

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 is

[OMPI devel] New "State" labels in github

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): https://github.com/open-mpi/ompi/wiki/SubmittingBug

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

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

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

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] Patcher on MacOS

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 w

Re: [OMPI devel] Patcher on MacOS

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 devel

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

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 (22

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

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] Openmpi configure: Could not determine the fortran compiler flag

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 precisely

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

p track of the 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 &g

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

> 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 to

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

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 Sq

[OMPI devel] 2.1.6rc1

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 hol

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

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] Did someone enable Travis?

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, i

Re: [OMPI devel] Did someone enable Travis?

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?

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 ch

[OMPI devel] For discussion on the Webex tomorrow

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

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 jsquy...@cisco.co

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

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 ___ dev

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

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] Location poll for April Open MPI dev face-to-face meeting

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 P

[OMPI devel] One-sided tests in MTT

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 jsquy...@cisco

[OMPI devel] MPIX FP16 datatypes

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 seems

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

worth running 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 -- >&

[OMPI devel] Open MPI face-to-face

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 deve

[OMPI devel] Queued up Open MPI mails

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 Squyre

[OMPI devel] Gentle reminder: sign up for the face to face

Gentle reminder to please sign up for the face-to-face meeting and add your items to the wiki: https://github.com/open-mpi/ompi/wiki/Meeting-2019-04 -- Jeff Squyres jsquy...@cisco.com ___ devel mailing list devel@lists.open-mpi.org https://lists.

Re: [OMPI devel] Help regarding Openmpi source code

Additionally, the code for implementing the PMPI interface is done through #define's. Depending on the platform, it happens either as Clement describes (with #defines for MPI_Foo --> PMPI_Foo) or if the platform doesn't support weak symbols (e.g., MacOS), the source code for the C API functions

[OMPI devel] Face to face meeting: need agenda items

Folks -- The agenda for the face-to-face meeting is pretty light (https://github.com/open-mpi/ompi/wiki/Meeting-2019-04). If we don't get enough items in the agenda, we might want to cancel the meeting. *** If you have agenda items, please put them on the wiki ASAP *** We should probably make

[OMPI devel] Proposal: Github "stale" bot

I have proposed the use of the Github Probot "stale" bot: https://probot.github.io/apps/stale/ https://github.com/open-mpi/ompi/pull/6495 The short version of what this bot does is: 1. After a period of inactivity, a label will be applied to mark an issue as stale, and optionally a comm

Re: [OMPI devel] Face to face meeting: need agenda items

I do not see any new additions to the agenda since last week: https://github.com/open-mpi/ompi/wiki/Meeting-2019-04 If we don't get a substantial set of new items on the agenda by tomorrow, it's going to be tempting to cancel this face-to-face meeting (i.e., defer it to summer/fall when we

Re: [OMPI devel] Face to face meeting: need agenda items

> On Mar 25, 2019, at 11:30 AM, Jeff Squyres (jsquyres) via devel > wrote: > > I do not see any new additions to the agenda since last week: > >https://github.com/open-mpi/ompi/wiki/Meeting-2019-04 > > If we don't get a substantial set of new items on the ag

Re: [OMPI devel] Fortran 2018 ISO_Fortran_binding.h will be available from gcc 9

To follow up for the web archives: see Gilles' PR for this in https://github.com/open-mpi/ompi/pull/6569. > On Apr 3, 2019, at 12:33 AM, Gilles Gouaillardet wrote: > > Folks, > > > FYI, and as posted by Damian Rouson in the de...@mpich.org ML > > >> The upcoming GCC 9 release will contain

Re: [OMPI devel] Incomplete MPI-1 removal

Thanks for the heads-up. Gilles made a first PR: https://github.com/open-mpi/ompi/pull/6626 > On Apr 27, 2019, at 7:14 AM, Lisandro Dalcin via devel > wrote: > > All the symbols below are legacy MPI-1 stuff, then should go away, marked as > deprecated, etc. > > $ grep "MPI_COMBINER_[HS].*_

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

I've made a Doodle to select a week for a Fall 2019 face-to-face meeting (assume we'll do the usual Tue-Thu meeting): https://github.com/open-mpi/ompi/wiki/Meeting-2019-Fall Please fill it out by next Tuesday, May 7, 2019. Thanks! -- Jeff Squyres jsquy...@cisco.com __

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

We decided today to have the next face-to-face meeting the week of August 12 (see https://github.com/open-mpi/ompi/wiki/Meeting-2019-Fall). Now we're opening the discussion of where the meeting will be. Two organizations have volunteered: - Cisco / San Jose - IBM / Dallas If anyone else would

Re: [OMPI devel] Next Open MPI dev face-to-face

Some availability changed and we might need to reneg on the week of August 12. The new proposal is the week of September 16th. > On May 14, 2019, at 8:53 AM, Jeff Squyres (jsquyres) via devel > wrote: > > We decided today to have the next face-to-face meeting the week of Augus

[OMPI devel] Fwd: Details on the Scan.coverity.com June 2019 Upgrade

FYI. Begin forwarded message: From: "Peter Degen-Portnoy " mailto:n...@go2.synopsys.com>> Subject: Details on the Scan.coverity.com June 2019 Upgrade Date: June 12, 2019 at 3:16:23 PM EDT To: jsquy...@cisco.com Reply-To: "SynopsysSIG" mailto

[OMPI devel] Do we need a fall face-to-face meeting?

We're talking through the scheduling of a potential fall face-to-face meeting. In doing so, we're wondering if we actually need it (recall: we turned out to not need the spring meeting). We copied the small set of items on the spring agenda wiki to the proposed fall agenda wiki, and are wonderi

Re: [OMPI devel] Do we need a fall face-to-face meeting?

We need to make a decision on whether to have a fall meeting or not. Please add agenda items to the wiki by COB **tomorrow**, Wednesday, 26 June 2019: https://github.com/open-mpi/ompi/wiki/Meeting-2019-Fall Thanks. > On Jun 24, 2019, at 12:42 PM, Jeff Squyres (jsquyres) via de

Re: [OMPI devel] Do we need a fall face-to-face meeting?

n on whether to have a fall meeting or not. > > Please add agenda items to the wiki by COB **tomorrow**, Wednesday, 26 June > 2019: > >https://github.com/open-mpi/ompi/wiki/Meeting-2019-Fall > > Thanks. > > > > >> On Jun 24, 2019, at 12:42 PM, Jeff

[OMPI devel] Face-to-face discussions of ORTE/PRRTE issues: Doodle

Per Teleconf discussions, we have canceled the general face-to-face meeting for this Fall, but we still have pressing issues that need to be decided about PRRTE and ORTE. We need a face-to-face meeting for this. We anticipate this will be a 2-full-day meeting. 1. Here's a Doodle to select the

Re: [OMPI devel] Build fails for Git versions (master and v4.0.x)

This is very odd. I do not see any obvious bad output in any of your logs. Also, the missing symbols below are only *some* of the OPAL components. Why only those? Also, why is libopen-pal.so looking for those symbols in the first place? All those symbols are in plugins / components -- they'r

Re: [OMPI devel] Build fails for Git versions (master and v4.0.x)

On Jul 31, 2019, at 5:44 PM, Jan Bierbaum wrote: > > Thanks a lot. This completely fixed those build problems. I used 'git > clean -df' (without x) before and could have sworn I also tried a fresh > clone … well, obviously I hadn't. Ah ha! Ok, good. Because I was seriously stumped there. Not

Re: [OMPI devel] Debug options break build

I am unable to reproduce these issues on master HEAD; assumedly they have something to do with UCX...? I filed https://github.com/open-mpi/ompi/issues/6995 to track the issue. On Sep 19, 2019, at 11:40 AM, Jan Bierbaum via devel mailto:devel@lists.open-mpi.org>> wrote: Switching on various de

Re: [OMPI devel] Debug options break build

On Sep 19, 2019, at 6:07 PM, Jan Bierbaum wrote: > > On 19.09.19 22:40, Jeff Squyres (jsquyres) wrote: >> I am unable to reproduce these issues on master HEAD; assumedly they have >> something to do with UCX...? >> I filed https://github.com/open-mpi/ompi/issues/6995 to track the issue. > Yes,

Re: [OMPI devel] hcoll missing libsharp

Can you send more detail? https://www.open-mpi.org/community/help/ On Oct 14, 2019, at 9:58 AM, Chris Ward via devel mailto:devel@lists.open-mpi.org>> wrote: One of my fellow developers at IBM is having problems building OpenMPI 4. The 'configure' command is failing trying to set up the mca h

Re: [OMPI devel] hcoll missing libsharp

Please send all the information listed at the https://www.open-mpi.org/community/help/ URL; thanks. On Oct 14, 2019, at 10:51 AM, Chris Ward mailto:t...@uk.ibm.com>> wrote: 'configure' ends with --- MCA component coll:hcoll (m4 configuration macro) checking for MCA component coll:hcoll compile

Re: [OMPI devel] hcoll missing libsharp

Thanks for the info. Looking at the config.log file, I can see it is trying several different ways to look for libhcoll. Here's one of them: configure:274258: gcc -std=gnu99 -std=gnu99 -o conftest -O3 -DNDEBUG -finline-functions -fno-strict-aliasing -mcx16 -pthread -I/install/u/tjcw/workspace

Re: [OMPI devel] hcoll missing libsharp

You *shouldn't* need to set LD_LIBRARY_PATH, because configure is not trying to actually run the test app that it is compiling. Indeed, it seems that the failure is occurring when it's trying to link (i.e., even if it was trying to run, it seems like the failure is before it would have tried to

Re: [OMPI devel] hcoll missing libsharp

On Oct 15, 2019, at 11:05 AM, Gilles GOUAILLARDET via devel mailto:devel@lists.open-mpi.org>> wrote: I agree we are not trying to run the binary here, but I am still puzzled here... Basically, gcc -o a.out foo.o -L/.../hcoll/lib -lhcoll and libhcoll.so depends on libsharp.so (that is in /.../

Re: [OMPI devel] hcoll missing libsharp

I don't see any other obvious issue here. Can someone from Mellanox reply? On Oct 15, 2019, at 10:53 AM, Chris Ward mailto:t...@uk.ibm.com>> wrote: -bash-4.2$ ls -l /install/u/tjcw/workspace/ibm_smpi_toucan_ucx/ompibase/dependencies/mofed_400/opt/mellanox/sharp/lib/libsharp_coll.so.2 lrwxrwx

[OMPI devel] Open MPI Winter 2020 face-to-face meeting

Dates and location have been decided: - Feb 17-18, 2020 (immediately prior to the MPI Forum meeting) - Portland, OR, USA Wiki page is up: https://github.com/open-mpi/ompi/wiki/Meeting-2020-02 1. Please put your name on the page if you plan to attend (so you can be registered as a guest) 2. Plea

[OMPI devel] Open MPI State of the Union BOF at SC'19

Be sure to come to the Open MPI State of the Union BOF at SC'19 next month! As usual, we'll discuss the current status and future roadmap for Open MPI, answer questions, and generally be available for discussion. The BOF will be in the Wednesday noon hour: https://sc19.supercomputing.org/sessio

[OMPI devel] Open MPI 3.0.5rc1 and 3.1.5rc1

v3.0.5rc1 and v3.1.5rc1 have both been posted. Please test. https://www.open-mpi.org/software/ompi/v3.0/ https://www.open-mpi.org/software/ompi/v3.1/ These are maintenance releases, containing a bunch of accumulated bug fixes. They should both be minor upgrades compared to their respec

Re: [OMPI devel] OMPI-5.0 vs. gfortran in RHEL

Fair enough. I updated the 5.0 wiki yesterday. On Nov 20, 2019, at 2:00 PM, Paul Hargrove via devel mailto:devel@lists.open-mpi.org>> wrote: All, Following up on my question in the OMPI BoF today, I have confirmed that RHEL8 is shipping GCC-8.2, not the problematic GCC-4.8.5 used in RHEL7.

[OMPI devel] Slides from the Open MPI SC'19 BOF

Thanks to all who came to see the Open MPI State of the Union BOF at SC'19 in Denver yesterday. I have posted the slides on the Open MPI web site -- that may take a little time to propagate out through the CDN to reach everyone, but they should show up soon: https://www.open-mpi.org/papers

Re: [OMPI devel] Initialization order between MPI and CUDA using Omni-Path

Thanks for the suggestion -- I filed https://github.com/open-mpi/ompi/issues/7240 to have Intel / Nvidia do this. On Dec 15, 2019, at 5:01 PM, PADIOLEAU Thomas via devel mailto:devel@lists.open-mpi.org>> wrote: Hello, I recently figured out that when running multi-GPU MPI application (one MPI

[OMPI devel] Cisco's MTT testing to be shut down for the holidays

Cisco will be disabling its MTT testing this evening for our holiday company-wide shutdown. I'll resume our MTT testing in January. -- Jeff Squyres jsquy...@cisco.com

Re: [OMPI devel] PMIX ERROR: INIT spurious message on 3.1.5

That actually looks like a legit error -- it's failing to initialize a shared mutex. I'm not sure what the consequence is of this failure, though, since the job seemed to run ok. Are you able to run multi-node jobs ok? > On Dec 22, 2019, at 1:20 AM, Marco Atzeri via devel > wrote: > > Hi D

  1   2   3   >