Bug#972385: petsc4py: autopkgtest failure on amd64: Caught signal number 11 SEGV

[Drew Parsons]

Seems the problem is that the kspsolve demo needs the number of 
processors to be a power of 2. Not 5, not 48.

Bug#972385: petsc4py: autopkgtest failure on amd64: Caught signal number 11 SEGV

[Drew Parsons]

Source: petsc4py
Followup-For: Bug #972385

When the petsc4py tests fail, it seems to correlate with
  mpiexec -n 48 python3 test_mat_cg.py
  
When the tests pass, they pass with
  mpiexec -n 2 python3 test_mat_cg.py
  
  
Evidently the MPI tests are calling on the full number of available
CPUs. The tests are not large enough to run successfully over 48
processes.

In that case we should be able to resolve the problem by constraining
the number of processes used with mpiexec.

Bug#972385: petsc4py: autopkgtest failure on amd64: Caught signal number 11 SEGV

[Aurelien Jarno]

Source: petsc4py
Version: 3.13.0-8
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-Cc: debian...@lists.debian.org

The autopkgtest for amd64 currently fail:
| python3 run_demo.py
| [0]PETSC ERROR: 

| [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, 
probably memory access out of range
| [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
| [0]PETSC ERROR: or see 
https://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
| [0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to 
find memory corruption errors
| [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and 
run 
| [0]PETSC ERROR: to get more information on the crash.
| --
| MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
| with errorcode 50162059.
| 
| NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
| You may or may not see output from other processes, depending on
| exactly when Open MPI kills them.
| --
| make[1]: *** [makefile:17: run] Error 139

See
https://ci.debian.net/data/autopkgtest/testing/amd64/p/petsc4py/7426792/log.gz
for the full log

Regards,
Aurelien