Hi Howard,
I’ve been playing with the same version of psm (hfi1-psm-0.7-221.ch6.x86_64)
but cannot yet reproduce the issue. Just in case, please share the version of
the driver you have installed (hfi1-X.XX-XX.x86_64.rpm, modinfo hfi1).
What I can tell so far, is that I still suspect this has
Not sure if Howard wants the check to be OFF by default in tarballs, or
absent completely.
I test almost exclusively from RC tarballs, and have access to many
uncommon platforms.
So, if you think it is useful for my testing to help look for these
warnings, then there should be some way to enable i
I also think this symbol checker should not be in the tarball.
Howard
2016-04-20 13:08 GMT-06:00 Jeff Squyres (jsquyres) :
> On Apr 20, 2016, at 2:08 PM, dpchoudh . wrote:
> >
> > Just to clarify, I was doing a build (after adding code to support a new
> transport) from code pulled from git (a
On Apr 20, 2016, at 2:08 PM, dpchoudh . wrote:
>
> Just to clarify, I was doing a build (after adding code to support a new
> transport) from code pulled from git (a 'git clone') when I came across this
> warning, so I suppose this would be a 'developer build'.
No worries. I only brought it u
Dear all
Just to clarify, I was doing a build (after adding code to support a new
transport) from code pulled from git (a 'git clone') when I came across
this warning, so I suppose this would be a 'developer build'.
I know I am not a real MPI developer (I am doing OMPI internal development
for th
> On Apr 20, 2016, at 10:24 AM, Dave Goodell (dgoodell)
> wrote:
>
> On Apr 20, 2016, at 9:14 AM, Jeff Squyres (jsquyres)
> wrote:
>>
>> I was under the impression that this warning script only ran for developer
>> builds. But it looks like it's unconditionally run at the end of "make
>>
On Apr 20, 2016, at 9:14 AM, Jeff Squyres (jsquyres) wrote:
>
> I was under the impression that this warning script only ran for developer
> builds. But it looks like it's unconditionally run at the end of "make
> install" (on master only -- so far).
>
> Should we make this only run for devel
Hello Alina,
Thank you for the information about how the pml components work. I knew
that the other components were being opened and ultimately closed in
favor of yalla, but I didn't realize that initial open would cause a
persistent change in the ompi runtime.
Here's the information you req
HI Matias,
Actually I found the problem. I kept wondering why the OFI MTL works fine,
but the
PSM2 MTL doesn't. When I cranked up the debugging level I noticed that for
OFI MTL,
it doesn't mess with the PSM2_DEVICES env variable. So the PSM2 tries all
three
"devices" as part of initialization.
Agreed - it was only supposed to run for developer builds
> On Apr 20, 2016, at 7:14 AM, Jeff Squyres (jsquyres)
> wrote:
>
> I was under the impression that this warning script only ran for developer
> builds. But it looks like it's unconditionally run at the end of "make
> install" (on mas
I was under the impression that this warning script only ran for developer
builds. But it looks like it's unconditionally run at the end of "make
install" (on master only -- so far).
Should we make this only run for developer builds? (e.g., check for
$srcdir/.git, or somesuch) I think it's o
Hi David,
I was able to reproduce the issue you reported.
When the command line doesn't specify the components to use, ompi will try
to load/open all the ones available (and close them in the end) and then
choose the components according to their priority and whether or not they
were opened succe
Hi, David
We are looking into your report.
Best,
Josh
On Tue, Apr 19, 2016 at 4:41 PM, David Shrader wrote:
> Hello,
>
> I have been investigating using XRC on a cluster with a mellanox
> interconnect. I have found that in a certain situation I get a seg fault. I
> am using 1.10.2 compiled wi
13 matches
Mail list logo
