Solution to issue cannot be found in the documentation.
[X] I checked the documentation.
Issue
There appears to be a problem in scotch on the mac-arm builds of scotch.
It's very likely this is not a dolfinx bug, but rather a bug in scotch and/or petsc, but saving here for tracking and discovery.
Running pytest unit/mesh/test_mesh_partitioners.py segfaults with
ERROR: SCOTCH_dgraphMapInit: internal error
[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.
[0]PETSC ERROR: Run with -malloc_debug to check if memory corruption is causing the crash.
Abort(59) on node 0 (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0
Parititoning with parmetis and kahip both seem to work.
I'm not sure if I can disable scotch in the build so it will be unavailable instead of, since petsc is built with it.
scotch is disabled now for osx-arm64 builds and other openmpi builds, which were apparently failing to be found. The new strict -DDOLFINX_ENABLE_SCOTCH helped reveal that, yay!
Solution to issue cannot be found in the documentation.
Issue
There appears to be a problem in scotch on the mac-arm builds of scotch.
It's very likely this is not a dolfinx bug, but rather a bug in scotch and/or petsc, but saving here for tracking and discovery.
Running
pytest unit/mesh/test_mesh_partitioners.py
segfaults withParititoning with parmetis and kahip both seem to work.
I'm not sure if I can disable scotch in the build so it will be unavailable instead of, since petsc is built with it.
Installed packages
Environment info