Kevin,
you should only use the tarballs from www.open-mpi.org
they are generated with our scripts.
if i understand correctly, github.com has its own way of generating a
tarball from a git tag.
Cheers,
Gilles
On 3/31/2017 1:24 PM, Kevin Buckley wrote:
On 29 March 2017 at 13:49, Jeff
On 29 March 2017 at 13:49, Jeff Squyres (jsquyres) wrote:
> I have no objections to this.
>
> Unfortunately, I don't have the time to work on it, but we'd be glad to look
> at pull requests to introduce this functionality. :-)
Yes, yes, alright.
I am though slightly
Yeah, sorry about that; we had a configuration issue while trying to clean up
some issues on the server which hosts the OMPI Jenkins install. It should be
back to normal now.
Brian
On Mar 30, 2017, at 11:46 AM, Howard Pritchard
> wrote:
well
well not sure what's going on. there was an upgrade of jenkins a bunch of
functionality seems to have gotten lost.
2017-03-30 9:37 GMT-06:00 Howard Pritchard :
> Actually it looks like we're running out of disk space at AWS.
>
>
> 2017-03-30 9:28 GMT-06:00
Actually it looks like we're running out of disk space at AWS.
2017-03-30 9:28 GMT-06:00 r...@open-mpi.org :
> You didn’t do anything wrong - the Jenkins test server at LANL is having a
> problem.
>
> On Mar 30, 2017, at 8:22 AM, DERBEY, NADIA wrote:
>
You didn’t do anything wrong - the Jenkins test server at LANL is having a
problem.
> On Mar 30, 2017, at 8:22 AM, DERBEY, NADIA wrote:
>
> Hi,
>
> I just created a pull request and I have a failure in 4/8 checks, all related
> to LANL:
>
> LANL-CI
> LANL-OS-X
>
Hi,
I just created a pull request and I have a failure in 4/8 checks, all related
to LANL:
LANL-CI
LANL-OS-X
LANL-disable-dlopen
LANL-distcheck
When I ask for the failures details, I repectively get the following messages:
==
...
libtoolize: copying file
Hello,
I am using the git version of MPI with "-bind-to core -report-bindings"
and I get that for all processes:
[miriel010:160662] MCW rank 0 not bound
When I use an old version I get:
[miriel010:44921] MCW rank 0 bound to socket 0[core 0[hwt 0]]:
Hello,
when I went back to this problem, the segfault did not happen again...
I do not know why, but I am glad with that.
Cyril.
Le 13/02/2017 à 10:15, Cyril Bordage a écrit :
> Unfortunately this does not complete this thread. The problem is not
> solved! It is not an installation problem. I