Awesome! BTW, you added some generated files and other files by mistake (.deps,
Makefile, Makefile.in, configure.params).
-Nathan
On Mon, Jul 01, 2013 at 06:39:44PM -0400, svn-commit-mai...@open-mpi.org wrote:
> Author: jladd (Joshua Ladd)
> Date: 2013-07-01 18:39:43 EDT (Mon, 01 Jul 2013)
> New
As all examples are working perfectly in my version of the code I was puzzled
by Jeff's issue. It turns out it's a side effect of trying to push as few items
as possible instead of just pushing everything in the trunk. I'll fix it in few
minutes, meanwhile I'll drop few words about what was the
Vasily, I am not able to reproduce this at all. I just did a fresh checkout of
the trunk. As explained, it was truncated. I did as Jeff and Brian suggested
and did 'svn up .' a couple of times (had to do 'svn cleanup' first to unlock
some files apparently). I did a vpath build as you describe, a
Thank you, Jeff. However, I've got it working by rewriting 'include'
strings in 'autogen_found_items.m4' from relative to absolute paths.
As the M4 file is being, actually, generated rather than it exists in
the svn tree, one has a short temporal window, just few seconds before
it's getting execute
On 7/1/13 9:52 AM, "Joshua Ladd" wrote:
>I think we (MLNX) are getting corrupted/truncated checkouts. Lately, I
>have been running into the following error on our internal systems when
>doing a secure checkout:
>
>svn co https://svn.open-mpi.org/svn/ompi/trunk ompi-trunk
>
>svn: E175002: REPORT o
That has happened to me periodically; I've usually been able to cd into the SVN
dir and "svn up" to complete the checkout.
On Jul 1, 2013, at 11:52 AM, Joshua Ladd wrote:
> I think we (MLNX) are getting corrupted/truncated checkouts. Lately, I have
> been running into the following error on o
I think we (MLNX) are getting corrupted/truncated checkouts. Lately, I have
been running into the following error on our internal systems when doing a
secure checkout:
svn co https://svn.open-mpi.org/svn/ompi/trunk ompi-trunk
svn: E175002: REPORT of '/svn/ompi/!svn/vcc/default': Could not read
If it helps, here's the output from when I run autogen.
On Jul 1, 2013, at 10:57 AM, Ralph Castain wrote:
> Hmmm...well, I'm not sure what I can do to help. I have to agree with Jeff
> that something has gotten really messed up in your checkout or system. You
> might check to ensure you are
Open MPI version:1.7.2 on IB system.
Test: everybody sends to everybody - Irecv, Isend, Wait. In total 1024 process.
Warning:
"[warn] opal_libevent2019 each event_base at once.
[warn] opal_libevent2019_event_base_loop: reentrant invocation. Only one
event_base_loop can run on each event_base a
Hmmm...well, I'm not sure what I can do to help. I have to agree with Jeff that
something has gotten really messed up in your checkout or system. You might
check to ensure you are picking up the right autotools, and perhaps re-checkout
the trunk.
All I can tell you is that it is building just f
Dear Ralph, I believe I have run autogen.pl after a fresh full
checkout, and not yet after an update:
Open MPI autogen (buckle up!)
1. Checking tool versions
Searching for autoconf
...
- from my log
How ../../config/autogen_found_items.m4:274 is supposed to find
'opal/mca/backtrace/configur
Per Ralph's suggestion, it sounds like autogen.pl may not have been run, or may
not have succeeded...?
On Jul 1, 2013, at 10:11 AM, Vasiliy
wrote:
> As I wrote it, it *does* exist in it's place, but it's the configure
> script which couldn't find it; and, yes, I've made a fresh checkout.
>
>
As I wrote it, it *does* exist in it's place, but it's the configure
script which couldn't find it; and, yes, I've made a fresh checkout.
On Mon, Jul 1, 2013 at 4:02 PM, Jeff Squyres (jsquyres)
wrote:
> Sounds like you have a busted SVN checkout -- that file exists for me:
>
> [10:02] jsquyres-ma
Or you might try rerunning autogen.pl in case you updated and didn't catch that
something requiring autogen changed
On Jul 1, 2013, at 7:02 AM, "Jeff Squyres (jsquyres)"
wrote:
> Sounds like you have a busted SVN checkout -- that file exists for me:
>
> [10:02] jsquyres-mac:~/s/ompi3 ❯❯❯ svnv
Sounds like you have a busted SVN checkout -- that file exists for me:
[10:02] jsquyres-mac:~/s/ompi3 ❯❯❯ svnversion .
28688
[10:02] jsquyres-mac:~/s/ompi3 ❯❯❯ svn info opal/mca/backtrace/configure.m4
Path: opal/mca/backtrace/configure.m4
Name: configure.m4
Working Copy Root Path: /Users/jsquyres/
Hello,
There is an error while configuring OpenMPI from the svn checkout with
aclocal not being able to find 'opal/mca/backtrace/configure.m4',
which, in fact, does exist there. What changes are needed to fix that?
Note: it has stepped in the 'opal/libltdl' directory just before that error:
***
George --
All 4 tests fail for me -- can you have a look?
-
[6:50] savbu-usnic-a:~/s/o/dist_graph ❯❯❯ mpirun --mca btl tcp,sm,self --host
mpi001,mpi002,mpi003,mpi004 -np 5 --bynode distgraph_test_1
[mpi002:5304] *** An error occurred in MPI_Dist_graph_create
[mpi002:5304] *** reported by pro
Yes, Bruck for barrier is a variant of the dissemination algorithm as described
in:
- Debra Hensgen, Raphael Finkel, and Udi Manbet. Two algorithms for barrier
synchronization. International Journal of Parallel Programming, 17(1):1–17,
1988.
George.
On Jun 29, 2013, at 12:05 , Ronny Brende
The patch has been pushed into the trunk in r28687.
George.
On Jul 1, 2013, at 13:55 , George Bosilca wrote:
> Guys,
>
> Thanks for the patch and for the tests. All these changes/cleanups are
> correct, I have incorporate them all in the patch. Please find below the new
> patch.
>
> As t
Ahem …
George.
topo.patch
Description: Binary data
On Jul 1, 2013, at 13:55 , George Bosilca wrote:
> Guys,
>
> Thanks for the patch and for the tests. All these changes/cleanups are
> correct, I have incorporate them all in the patch. Please find below the new
> patch.
>
> As the dead
Guys,
Thanks for the patch and for the tests. All these changes/cleanups are correct,
I have incorporate them all in the patch. Please find below the new patch.
As the deadline for the RFC is today, I'll move forward and push the changes
into the trunk, and if there are still issues we can work
George,
My colleague was working on your ompi-topo bitbucket repository
but it was not completed. But he found bugs in your patch attached
in your previous mail and created the fixing patch. See the attached
patch, which is a patch against Open MPI trunk + your patch.
His test programs are also a
22 matches
Mail list logo
