[OMPI devel] master nightly tarballs stopped on 11/21

Hi Brian, Could you check what’s going on with the nightly tarball builds? Nothing new has been built since 11/21 even though a number of PR’s have been merged in since then. Thanks, Howard -- Howard Pritchard HPC-DES Los Alamos National Laboratory

Re: [OMPI devel] Developing MPI program without mpirun

Hello Rui, Note there is no standard for the format of the port_name so don’t read much what it looks like when printed out. Could you provide some more information about your particular setup: - characteristics of the system you are using, e.g. a Linux cluster, laptop running os-x, etc. -

Re: [OMPI devel] Failure while loading shmem module

running v.1.10.0rc7? It's a custom version, we didn't modify spml or sm related code though. 2016-11-15 14:12 GMT+01:00 Pritchard Jr., Howard <howa...@lanl.gov<mailto:howa...@lanl.gov>>: HI Gianmario, Probably something went wrong at the spml layer. Could you also add —mac spml_base_ver

Re: [OMPI devel] Failure while loading shmem module

HI Gianmario, Probably something went wrong at the spml layer. Could you also add —mac spml_base_verbose 10 to the job launch line? Howard -- Howard Pritchard HPC-DES Los Alamos National Laboratory From: devel > on

Re: [OMPI devel] regression: MPI_Neighbor_alltoall with empty graph

Hi Daniel, Thanks very much for trying 2.0.1 out and reporting this. Looks like this may be a case of not checking “edge” cases in the use of this collective. Would you please open an issue? There is currently an issue 2324 related to neighbor collectives, but it isn’t directly related to the

[OMPI devel] direct launch problem with master

Hi Folks, While trying to solve a different problem, I optimistically tried to use head-of –master to work on that problem. Now I’ve found a new problem with master when trying to do a direct launch with SLURM, srun: [nid00012:09456] [[27960,0],0] ERROR: Failed to identify the local daemon's

Re: [OMPI devel] OpenGrok (?)

Hi Jeff, I’m not using it. Howard -- Howard Pritchard HPC-DES Los Alamos National Laboratory On 10/19/16, 9:21 AM, "devel on behalf of Jeff Squyres (jsquyres)" wrote: >Looking through the OpenGrok requirements, I have to

Re: [OMPI devel] Lots of new features rolled out on github.com today

Ralph, I know with older versions of git you may have problems since you can’t use https. I think with newer versions it will prompt not just for passed but also 2-factor. That’s one problem I hit anyway when first enabling 2-factor. Howard -- Howard Pritchard HPC-DES Los Alamos National

Re: [OMPI devel] PMIx Language Bindings

HI Ralph, If the java bindings are of use, I could see if my student how did a lot of the recent work in the Open MPI java bindings would be interested. He doesn¹t have a lot of extra cycles at the moment though. Howard -- Howard Pritchard HPC-DES Los Alamos National Laboratory On

Re: [OMPI devel] tcp btl rendezvous performance question

Hi Sreenidhi Only partial resolution. By pushing out the eager path to 4 MB we were able to get around 2GB/sec per socket connection with osu bw test. The kernel is quite old though - 2.6.x - and being a summer student project with a focus on IB vs rout able ROCE we've moved on. Howard

[OMPI devel] LANL jenkins update

Hi Folks, The LANL/(soon to not be iu) jenkins should now work with bot:lanl:retest Also, NERSC Cori system went down this morning for maintenance during CI check of PR 1896 on master. I didn't see any others impacted by the cori maintenance. Howard -- Howard Pritchard HPC-DES Los Alamos

Re: [OMPI devel] 2.0.0rc4 Crash in MPI_File_write_all_end

Jeff, I think this was fixed in PR 1227 on v2.x Howard -- Howard Pritchard HPC-DES Los Alamos National Laboratory On 7/13/16, 1:47 PM, "devel on behalf of Jeff Squyres (jsquyres)" wrote: >I literally just noticed that this

Re: [OMPI devel] Github migration: tomorrow

Hi Jeff, When's the latest today that we can do checkins without causing problems? Howard -Original Message- From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Jeff Squyres (jsquyres) Sent: Tuesday, September 30, 2014 9:57 AM To: Open MPI Developers List Subject: [OMPI

Re: [OMPI devel] [patch] libnbc intercommunicator iallgather bug

Hi Takahiro, Thanks very much for the patch and the test! After the git migration we'll open an issue and patch nbc_iallgather. This will get pushed to 1.8.4. Howard -Original Message- From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Kawashima, Takahiro Sent: Monday,

Re: [OMPI devel] [OMPI svn-full] svn:open-mpi r32814 - trunk/ompi/mca/coll/ml

Hi Jeff, Sure if that's the preferred check inside ompi itself. Howard -Original Message- From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Jeff Squyres (jsquyres) Sent: Monday, September 29, 2014 3:59 PM To: Open MPI Developers List Subject: Re: [OMPI devel] [OMPI svn-full]

[OMPI devel] release 1.9

Hi Folks, The release managers for the 1.9/2.0 stream have been putting together notes on features for this series, what sort of code pruning to do, etc. See https://github.com/open-mpi/ompi/wiki/Releasev19 We will be discussing the contents of the table(s) at the bottom of the wiki at

[OMPI devel] dfference between my_node_rank and my_local_rank in orte proc_info_t

Hi Folks, I'm trying to figure out something about the kind of info pmi's are suppose to be feeding back up in to orte/ompi, partly because native launch doesn't seem to work too well in trunk. One of the things I'm puzzling about is the purpose of the my_node_rank field in orte_proc_info_t.

Re: [OMPI devel] RFC: "v1.9.0" (vs. "v1.9")

Hi Folks, I thought that 1.9.X release would at some point become the 2.0 release. I thought trunk would go to 2.1 once we branch 1.9 from trunk, no? What Jeff and I don't like is using 1.9 with implicit 0, then having 1.9.1,1.9.2, etc. Howard -Original Message- From: devel

Re: [OMPI devel] RFC: remove the --with-threads configure option

I second the motion. -Original Message- From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain Sent: Thursday, September 18, 2014 8:43 AM To: Open MPI Developers Subject: Re: [OMPI devel] RFC: remove the --with-threads configure option None that I can think of - I'd

[OMPI devel] PSM MTl work with srun launch?

Hi Folks, I'm getting questions about the 1.8.2 and mtl psm and slurm-direct (srun) launch. User is hitting the problem that the global id is not being set. I've suggested for now that the user just set the OMPI_MCA_orte_precondition_transports environment variable for now to something like

Re: [OMPI devel] coll ml error with some nonblocking collectives

collectives Confirmed that trunk version r32658 does pass the test. From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Pritchard Jr., Howard Sent: Monday, September 15, 2014 4:16 PM To: Open MPI Developers Subject: Re: [OMPI devel] coll ml error with some nonblocking collectives Hi Rolf

Re: [OMPI devel] coll ml error with some nonblocking collectives

Hi Rolf, This may be related to change set 32659. If you back this change out, do the tests pass? Howard From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Rolf vandeVaart Sent: Monday, September 15, 2014 8:55 AM To: de...@open-mpi.org Subject: [OMPI devel] coll ml error with

[OMPI devel] mpirun + aprun question

Hi Folks, So, I've got a testbed cray system with no batch scheduler, just use the native alps both as the resource manager and as the job launcher for the orte daemons. What I'm noticing is that the mpirun command and -host option, or otherwise trying to specify via an mpirun way, the nodes to

Re: [OMPI devel] [OMPI svn-full] svn:open-mpi r32711 - trunk/opal/mca/pmix/cray

thanks, it was bad cut/paste From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Tim Mattox Sent: Thursday, September 11, 2014 2:54 PM To: Open MPI Developers Subject: Re: [OMPI devel] [OMPI svn-full] svn:open-mpi r32711 - trunk/opal/mca/pmix/cray I'm sure that is not what you meant to

Re: [OMPI devel] Need to know your Github ID

hppritcha->hppritcha -Original Message- From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Jeff Squyres (jsquyres) Sent: Wednesday, September 10, 2014 4:46 AM To: Open MPI Developers List Subject: [OMPI devel] Need to know your Github ID As the next step of the planned

Re: [OMPI devel] segfault in openib component on trunk

Hi Edgar, Could you send me your conf file? I'll try to reproduce it. Maybe run with --mca btl_base_verbose 20 or something to see what the code that is parsing this field in the conf file is finding. Howard -Original Message- From: devel [mailto:devel-boun...@open-mpi.org] On

Re: [OMPI devel] RFC: Merge PMIx branch to trunk

Hi Ralph, I would also add that the branch has the advantage that one can actually launch jobs on crays using aprun. That direct launch capability is busted in trunk at this point. Howard From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain Sent: Thursday, August 14,

[OMPI devel] btl thread safety question

Hi Folks, Has anyone checked about ompi thread safety support since the BTL move? I can only get the osu latency mt test to work using sm/shmem/vader. With TCP I see it hang after 32KB messages. Howard - Howard Pritchard HPC-5 Los Alamos

Re: [OMPI devel] v1.8.2 still held up...

Hi Ralph, I'll review 4826 as proxy for hjelmn. I'm just checking that it builds on my system before saying okay. Howard From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain Sent: Thursday, August 07, 2014 11:55 AM To: Open MPI Developers Subject: [OMPI devel] v1.8.2

Re: [OMPI devel] opal_config_bottom.h question again

ANY other files, nor should it include "opal_config.h". * */ Don't know why someone did that, but you might see if it fixes your problem On Aug 4, 2014, at 9:00 AM, Pritchard Jr., Howard <howa...@lanl.gov<mailto:howa...@lanl.gov>> wrote: Hi Folks, As I said last week,

[OMPI devel] opal_config_bottom.h question again

Hi Folks, As I said last week, I'm noticing now that on my opensuse 13.1 system and gcc 4.8.1, when I do a fresh checkout of trunk ompi and try to build, without any configure options, mca_base_mpool_frame.c does not compile. The reason is there is a conflict in opal_config_bottom.h and the

Re: [OMPI devel] openmpi-1.8.2rc2 and f08 interface built with PGI-14.7 causes link error

Sorry, finally got through all this ompi email and see this problem was fixed. -Original Message- From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Pritchard Jr., Howard Sent: Friday, August 01, 2014 8:59 AM To: Open MPI Developers Subject: Re: [OMPI devel] openmpi-1.8.2rc2

Re: [OMPI devel] openmpi-1.8.2rc2 and f08 interface built with PGI-14.7 causes link error

Hi Jeff, Finally got info yesterday about where the newer PGI compilers are hiding out at LANL. I'll check this out today. Howard -Original Message- From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Jeff Squyres (jsquyres) Sent: Tuesday, July 29, 2014 5:24 PM To: Open MPI

Re: [OMPI devel] RFC: job size info in OPAL

: Re: [OMPI devel] RFC: job size info in OPAL What is your definition of "global job size"? George. On Jul 31, 2014, at 11:06 , Pritchard Jr., Howard <howa...@lanl.gov> wrote: > Hi Folks, > > I think given the way we want to use the btl's in lower levels like > o

Re: [OMPI devel] RFC: job size info in OPAL

Hi Folks, I think given the way we want to use the btl's in lower levels like opal, it is pretty disgusting for a btl to need to figure out on its own something like a "global job size". That's not its business. Can't we add some attributes to the component's initialization method that

Re: [OMPI devel] OMPI_XXX defines in opal_config.h.in question

ge. On Tue, Jul 29, 2014 at 3:58 PM, Pritchard Jr., Howard <howa...@lanl.gov<mailto:howa...@lanl.gov>> wrote: Hi Folks, So I'm trying to get my pmix project back in order after making the big mistake of pulling in the BTL move stuff. I get bizillions of warning messages from the comp

[OMPI devel] OMPI_XXX defines in opal_config.h.in question

Hi Folks, So I'm trying to get my pmix project back in order after making the big mistake of pulling in the BTL move stuff. I get bizillions of warning messages from the compiler now about undefined macros. A number of the culprits are in opal_config.h.in, and begin with OMPI, like

Re: [OMPI devel] SHMEM symmetric objects in shared libraries

Hi Pasha, It can be done. Cray Fortran 2008 compiler had to do this to be fully compliant with the Fortran 2008 co-array feature. Howard -Original Message- From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Shamis, Pavel Sent: Tuesday, July 29, 2014 12:02 PM To: Open MPI

Re: [OMPI devel] SHMEM symmetric objects in shared libraries

Hi Josh, No, I think what Bert is talking about is having something like foobar.c == #include “shmem.h” long my_dso_val = 0; int foobar(void) { printf(“Hello from a shared library\n”); } == cc –fPIC –c foobar.c cc –shared –o libfoobar.so foobar.o cc –o

[OMPI devel] opal_config_bottom.h problem with trunk

Hi Folks, I was feeling lucky and decided to a fresh svn checkout of trunk and simple ./autogen.pl, ./configure make on a opensuse 13.1. I get a blowup in opal_config_bottom.h: pp@hagel-vm:~>../../opal/include/opal_config_bottom.h:383:38: error: expected declaration specifiers or '...' before