limited number of hosts, it seems to
behave as expected. Thanks!! Tom
--- On Mon, 8/18/08, George Bosilca wrote:
From: George Bosilca
Subject: Re: [OMPI users] MPI_ERR_TRUNCATE with MPI_Revc without Infinipath
To: "Open MPI Users"
Cc: "Tom Riddle"
List-Post: users@lis
chines without . I
guess I wonder what is the mechanism when in a wildcard mode.
--- On Sun, 8/17/08, George Bosilca wrote:
From: George Bosilca
Subject: Re: [OMPI users] MPI_ERR_TRUNCATE with MPI_Revc without
Infinipath
To: rarebit...@yahoo.com, "Open MPI Users"
Date: Sunday
Things were working without issue until we went to the wildcard MPI_ANY_SOURCE
on our receives but only on machines without . I guess I wonder what is the
mechanism when in a wildcard mode.
--- On Sun, 8/17/08, George Bosilca wrote:
From: George Bosilca
Subject: Re: [OMPI users] MPI_ERR_TRUNCATE w
Tom,
I did the same modification as you on the osu_latency and the
resulting application run to completion. I don't get any TRUNCATE
error messages. I'm using the latest version of Open MPI (1.4a1r19313).
There was a bug that might be related to your problem but our commit
log shows it wa
Hi,
A bit more info wrt the question below. I have run other releases of OpenMPI
and they seem to be fine. The reason I need to run the latest is because it
supports valgrind fully.
openmpi-1.2.4
openmpi-1.3ar18303
TIA, Tom
--- On Tue, 8/12/08, Tom Riddle wrote:
Hi,
I am getting a curious
Hi,
I am getting a curious error on a simple communications test. I have altered
the std mvapich osu_latency test to accept receives from any source and I get
the following error
[d013.sc.net:15455] *** An error occurred in MPI_Recv
[d013.sc.net:15455] *** on communicator MPI_COMM_WORLD
[d013.s
