Hi all.Recently, i see following error (No PMIx server was reachable) with NPICH only:
``` + export PETSC_ARCH=x86_64 + PETSC_ARCH=x86_64 + export PETSC_DIR=./ + PETSC_DIR=./+ export PYTHONPATH=/builddir/build/BUILD/petsc-3.23.6-build/BUILDROOT/usr/lib64/python3.14/site-packages/mpich + PYTHONPATH=/builddir/build/BUILD/petsc-3.23.6-build/BUILDROOT/usr/lib64/python3.14/site-packages/mpich + export LD_LIBRARY_PATH=/builddir/build/BUILD/petsc-3.23.6-build/BUILDROOT/usr/lib64/mpich/lib + LD_LIBRARY_PATH=/builddir/build/BUILD/petsc-3.23.6-build/BUILDROOT/usr/lib64/mpich/lib
+ export MPIEXEC=/usr/lib64/mpich/bin/mpiexec + MPIEXEC=/usr/lib64/mpich/bin/mpiexec + export PMIX_MCA_gds=hash + PMIX_MCA_gds=hash + make V=0 petsc4pytest PETSC4PY_NP=4/usr/bin/python3 .//config/gmakegentest.py --petsc-dir=./ --petsc-arch=x86_64 --testdir=./x86_64/tests --srcdir /builddir/build/BUILD/petsc-3.23.6-build/petsc-3.23.6/buildmpich_dir/src --pkg-pkgs "sys vec mat dm ksp snes ts tao"
*** Testing petsc4py on 4 processes *** No PMIx server was reachable, but a PMI1/2 was detected. If srun is being used to launch application, 4 singletons will be started.[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://petsc.org/release/faq/#valgrind and https://petsc.org/release/faq/ [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 Proc: [[1910,0],0] Errorcode: 59 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. --------------------------------------------------------------------------[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://petsc.org/release/faq/#valgrind and https://petsc.org/release/faq/ [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 Proc: [[526,0],0] Errorcode: 59 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. --------------------------------------------------------------------------[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://petsc.org/release/faq/#valgrind and https://petsc.org/release/faq/ [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 Proc: [[2319,0],0] Errorcode: 59 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. --------------------------------------------------------------------------[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://petsc.org/release/faq/#valgrind and https://petsc.org/release/faq/ [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 Proc: [[61041,0],0] Errorcode: 59 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. ``` Is it a new MPICH functionality? -- --- Antonio Trande Fedora Project https://fedoraproject.org/wiki/User:Sagitter mailto: sagitter@xxxxxxxxxxxxxxxxx GPG key: 0x40FDA7B70789A9CD GPG keys server: https://keys.openpgp.org/
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
