[OMPI devel] RFC: AUTHORS revamp

2016-04-25 Thread Jeff Squyres (jsquyres)
I created a first cut at an AUTHORS revamp to show the correlation between email addresses used in git commit messages to individual names: https://github.com/open-mpi/ompi/pull/1581 Comments welcome (probably easier to comment on the PR itself, so that we can track the conversation). -- J

Re: [OMPI devel] 1.10.3rc MTT failures

2016-04-25 Thread Jeff Squyres (jsquyres)
On Apr 25, 2016, at 9:50 AM, Gilles Gouaillardet wrote: > > and fwiw, Jeff uses an internally mirrored repo for ompi-tests, so it Cisco > clusters should use the latest test suites. Correct. My local git mirrors update nightly. FWIW: This made a *huge* difference when we were using SVN for o

Re: [OMPI devel] 1.10.3rc MTT failures

2016-04-25 Thread Ralph Castain
FWIW: there seems to be some message attempting to be sent down to the child procs on termination that is causing that issue. I’m not sure where it comes from, but probably is due to the restoration of the usock OOB component. > On Apr 25, 2016, at 7:25 AM, Josh Hursey wrote: > > IBM had a st

Re: [OMPI devel] 1.10.3rc MTT failures

2016-04-25 Thread Josh Hursey
IBM had a stale version of ompi-tests. I have sync'ed that repo, and will try again later today. The loop spawn error will take some digging. I'll see what we can find. On Mon, Apr 25, 2016 at 9:14 AM, Gilles Gouaillardet < gilles.gouaillar...@gmail.com> wrote: > This is a known bug that is bein

Re: [OMPI devel] 1.10.3rc MTT failures

2016-04-25 Thread Ralph Castain
I beg to differ on the Cisco case - some of those errors come directly from the Cisco MTT. > On Apr 25, 2016, at 6:50 AM, Gilles Gouaillardet > wrote: > > Cisco mtt looks clean > since ompi_tests repo is private, it cannot be automatically pulled unless a > password is saved (https) or a pub

Re: [OMPI devel] 1.10.3rc MTT failures

2016-04-25 Thread Gilles Gouaillardet
This is a known bug that is being discussed at https://github.com/open-mpi/ompi/pull/1473/commits/0d1431f02c6b2876cdeee4fd783d6b6807dfff2a it affects big endian machine or 8 bytes fortran integer Cheers, Gilles On Monday, April 25, 2016, Adrian Reber wrote: > Errors like that (Win::Get_attr: G

Re: [OMPI devel] 1.10.3rc MTT failures

2016-04-25 Thread Adrian Reber
Errors like that (Win::Get_attr: Got wrong value for disp unit) are from my ppc64 machine: https://mtt.open-mpi.org/index.php?do_redir=2295 The MTT setup is checking out the tests from github directly: [Test get: ibm] module = SCM scm_module = Git scm_url = https://github.com/open-mpi/ompi-tests.

[OMPI devel] 1.10.3rc MTT failures

2016-04-25 Thread Gilles Gouaillardet
Cisco mtt looks clean since ompi_tests repo is private, it cannot be automatically pulled unless a password is saved (https) or a public key was uploaded to github (ssh) for that reason, I would not simply assume the latest test suite is used :-( and fwiw, Jeff uses an internally mirrored repo for

Re: [OMPI devel] 1.10.3rc MTT failures

2016-04-25 Thread Ralph Castain
I don’t know - this isn’t on my machine, but rather in the weekend and nightly MTT reports. I’m assuming folks are running the latest test suite, but... > On Apr 25, 2016, at 6:20 AM, Gilles Gouaillardet > wrote: > > Ralph, > > can you make sure the ibm test suite is up to date ? > I pushed

Re: [OMPI devel] 1.10.3rc MTT failures

2016-04-25 Thread Gilles Gouaillardet
Ralph, can you make sure the ibm test suite is up to date ? I pushed a fix for datatypes a few days ago, and it should be fine now. I will double check this tomorrow anyway Cheers, Gilles On Monday, April 25, 2016, Ralph Castain wrote: > I’m seeing some consistent errors in the 1.10.3rc MTT

[OMPI devel] 1.10.3rc MTT failures

2016-04-25 Thread Ralph Castain
I’m seeing some consistent errors in the 1.10.3rc MTT results and would appreciate it if folks could check them out: ONESIDED: onesided/cxx_win_attr: [**ERROR**]: MPI_COMM_WORLD rank 0, file cxx_win_attr.cc:50: Win::Get_attr: Got wrong value for disp unit [**ERROR**]: MPI_COMM_WORLD rank 1, file