Eric,
can you please provide more information on how your tests are launched ?
do you
mpirun -np 1 ./a.out
or do you simply
./a.out
do you use a batch manager ? if yes, which one ?
do you run one test per job ? or multiple tests per job ?
how are these tests launched ?
do the test that
I should think we could pass the disable-pdl-open option downward - can’t see
any reason why not.
> On Sep 13, 2016, at 7:51 PM, Gilles Gouaillardet wrote:
>
> Folks,
>
>
> i configure'd Open MPI with
>
> --disable-shared --enable-static --disable-dlopen
>
> and i can no longer link a simpl
Folks,
i configure'd Open MPI with
--disable-shared --enable-static --disable-dlopen
and i can no longer link a simple MPI or OpenSHMEM app
$ mpicc -g -O0 -o hello_c ../../src/ompi-master/examples/hello_c.c
/usr/bin/ld:
/home/gilles/local/ompi-master-static/lib/libopen-pal.a(pdl_pdlopen_modu
On 13/09/16 12:11 PM, Pritchard Jr., Howard wrote:
Hello Eric,
Is the failure seen with the same two tests? Or is it random
which tests fail? If its not random, would you be able to post
No, the tests that failed were different ones...
the tests to the list?
Also, if possible, it would
Hello Eric,
Is the failure seen with the same two tests? Or is it random
which tests fail? If its not random, would you be able to post
the tests to the list?
Also, if possible, it would be great if you could test against a master
snapshot:
https://www.open-mpi.org/nightly/master/
Thanks,
Other relevant info: I never saw this problem with OpenMPI 1.6.5,1.8.4
and 1.10.[3,4] which runs the same test suite...
thanks,
Eric
On 13/09/16 11:35 AM, Eric Chamberland wrote:
Hi,
It is the third time this happened into the last 10 days.
While running nighlty tests (~2200), we have one
Hi,
It is the third time this happened into the last 10 days.
While running nighlty tests (~2200), we have one or two tests that fails
at the very beginning with this strange error:
[lorien:142766] [[9325,5754],0] usock_peer_recv_connect_ack: received
unexpected process identifier [[9325,0],
Hi every one,
As I was working and testing on the pml_monitoring mca component, I was
surprised to discover a failure in the error returning process.
As an example, using the ompi/test/monitoring/monitoring_test.c example,
if the directory does not exists, an error should be returned to the
