[petsc-dev] Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI process

Satish Balay balay at mcs.anl.gov
Sun Oct 9 11:16:30 CDT 2016


On Sun, 9 Oct 2016, Satish Balay wrote:

> On Sun, 9 Oct 2016, Antonio Trande wrote:
> 
> > 
> > PAPI disabled.
> > 
> > Please, see the result of testing at the bottom of this log:
> > https://copr-be.cloud.fedoraproject.org/results/sagitter/petsc/fedora-rawhide-x86_64/00462741-petsc/build.log.gz
> > 
> 
> Hm - the url is not working..
> 
> balay at asterix /home/balay/download-pine
> $ wget https://copr-be.cloud.fedoraproject.org/results/sagitter/petsc/fedora-rawhide-x86_64/00462741-petsc/build.log.gz
> --2016-10-09 10:40:43--  https://copr-be.cloud.fedoraproject.org/results/sagitter/petsc/fedora-rawhide-x86_64/00462741-petsc/build.log.gz
> Resolving copr-be.cloud.fedoraproject.org (copr-be.cloud.fedoraproject.org)... 209.132.184.48
> Connecting to copr-be.cloud.fedoraproject.org (copr-be.cloud.fedoraproject.org)|209.132.184.48|:443... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2016-10-09 10:40:45 ERROR 404: Not Found.

Perhaps you are refering to
http://copr-be.cloud.fedoraproject.org/results/sagitter/petsc/fedora-rawhide-x86_64/00462760-petsc/build.log.gz

>>>
+ make -C buildopenmpi_dir test 'MPIEXEC=/builddir/build/BUILD/petsc-3.7.3/buildopenmpi_dir/bin/petscmpiexec -np 4 -valgrind'
make: Entering directory '/builddir/build/BUILD/petsc-3.7.3/buildopenmpi_dir'
Running test examples to verify correct installation
Using PETSC_DIR=/builddir/build/BUILD/petsc-3.7.3/buildopenmpi_dir and PETSC_ARCH=x86_64
Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI process
See http://www.mcs.anl.gov/petsc/documentation/faq.html
Error in  mpiexec command: must start with -n <numberprocessors> or -valgrind -n <numberprocessors>
<<<<<

It should use "'MPIEXEC=/builddir/build/BUILD/petsc-3.7.3/buildopenmpi_dir/bin/petscmpiexec -valgrind'

I don't see anything else in the log thats suspicisous - but then - I'm not looking closely at everyting.

If there is something perticluar that I should look at - please copy/paste the relavent stuff for me..

Satish



More information about the petsc-dev mailing list