Bug#1127672: fenics-dolfinx FTBFS on 32-bit: test failures

Adrian Bunk bunk at debian.org
Wed Feb 11 13:54:40 GMT 2026


Source: fenics-dolfinx
Version: 1:0.10.0.post5-5
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Timo Röhling <roehling at debian.org>, Drew Parsons <dparsons at debian.org>

https://buildd.debian.org/status/fetch.php?pkg=fenics-dolfinx&arch=armhf&ver=1%3A0.10.0.post5-5%2Bb1&stamp=1770803493&raw=0

...
        part = _cpp.mesh.create_cell_partitioner(GhostMode.none)
        max_cells_per_facet = 2
>       mesh = create_mesh(
            MPI.COMM_WORLD,
            cells_np,
            [hexahedron._cpp_object, pyramid._cpp_object, tetrahedron._cpp_object],
            geomx,
            part,
            max_cells_per_facet,
        )
E       TypeError: create_mesh(): incompatible function arguments. The following argument types are supported:
E           1. create_mesh(arg0: MPICommWrapper, arg1: collections.abc.Sequence[ndarray[dtype=int64, shape=(*), order='C', writable=False]], arg2: collections.abc.Sequence[dolfinx.cpp.fem.CoordinateElement_float32], arg3: ndarray[dtype=float32, order='C', writable=False], arg4: collections.abc.Callable[[MPICommWrapper, int, collections.abc.Sequence[dolfinx.cpp.mesh.CellType], collections.abc.Sequence[numpy.ndarray[dtype=int64, writable=False]]], dolfinx.cpp.graph.AdjacencyList_int32], arg5: int | None) -> dolfinx.cpp.mesh.Mesh_float32
E           2. create_mesh(comm: MPICommWrapper, cells: ndarray[dtype=int64, shape=(*, *), order='C', writable=False], element: dolfinx.cpp.fem.CoordinateElement_float32, x: ndarray[dtype=float32, order='C', writable=False], partitioner: collections.abc.Callable[[MPICommWrapper, int, collections.abc.Sequence[dolfinx.cpp.mesh.CellType], collections.abc.Sequence[numpy.ndarray[dtype=int64, writable=False]]], dolfinx.cpp.graph.AdjacencyList_int32] | None, max_facet_to_cell_links: int | None = 2) -> dolfinx.cpp.mesh.Mesh_float32
E           3. create_mesh(arg0: MPICommWrapper, arg1: collections.abc.Sequence[ndarray[dtype=int64, shape=(*), order='C', writable=False]], arg2: collections.abc.Sequence[dolfinx.cpp.fem.CoordinateElement_float64], arg3: ndarray[dtype=float64, order='C', writable=False], arg4: collections.abc.Callable[[MPICommWrapper, int, collections.abc.Sequence[dolfinx.cpp.mesh.CellType], collections.abc.Sequence[numpy.ndarray[dtype=int64, writable=False]]], dolfinx.cpp.graph.AdjacencyList_int32], arg5: int | None) -> dolfinx.cpp.mesh.Mesh_float64
E           4. create_mesh(comm: MPICommWrapper, cells: ndarray[dtype=int64, shape=(*, *), order='C', writable=False], element: dolfinx.cpp.fem.CoordinateElement_float64, x: ndarray[dtype=float64, order='C', writable=False], partitioner: collections.abc.Callable[[MPICommWrapper, int, collections.abc.Sequence[dolfinx.cpp.mesh.CellType], collections.abc.Sequence[numpy.ndarray[dtype=int64, writable=False]]], dolfinx.cpp.graph.AdjacencyList_int32] | None, max_facet_to_cell_links: int | None = 2) -> dolfinx.cpp.mesh.Mesh_float64
E       
E       Invoked with types: Intracomm, list, list, ndarray, nanobind.nb_func, int
...
=========================== short test summary info ============================
FAILED test/unit/mesh/test_create_mixed_mesh.py::test_create_mixed_mesh - Typ...
ERROR test/unit/io/test_vtkhdf.py::test_read_write_mixed_topology - TypeError...
ERROR test/unit/io/test_vtkhdf.py::test_write_mixed_topology_data - TypeError...
ERROR test/unit/mesh/test_mixed_topology.py::test_mixed_cell_pairs - TypeErro...
ERROR test/unit/refinement/test_uniform.py::test_uniform_refine_mixed_mesh - ...
= 1 failed, 2847 passed, 100 skipped, 32 xfailed, 7 warnings, 4 errors in 1537.54s (0:25:37) =
E: pybuild pybuild:537: plugin pyproject failed: exit code=1: cd /build/reproducible-path/fenics-dolfinx-0.10.0.post5/.pybuild/cpython3_3.14_dolfinx-real/build; python3.14 -m pytest --durations=20 -k ""
make[1]: *** [debian/rules:171: debian/tmp-real] Error 14



This is the binNMU with nanobind 2.11.0, which might cause/trigger this failure.

On 32-bit MPICH is used instead of the 64-bit only OpenMPI, which might (or might not) be relevant.


More information about the debian-science-maintainers mailing list