Your message dated Sat, 10 Jan 2026 20:30:47 +0100
with message-id <[email protected]>
and subject line Re: dolfin: MPI tests fail against cmake-built HDF5: Unable to
write XDMF file
has caused the Debian Bug report #1125192,
regarding dolfin: MPI tests fail against cmake-built HDF5: Unable to write XDMF
file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1125192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125192
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: dolfin
Version: 2019.2.0~legacy20240219.1c52e83-26
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
A test-build of dolfin against cmake-built HDF5 (1.14.6 currently in
experimental) reported extraneaous MPI test failures.
All these new failures have this message logged:
*** Error: Unable to write XDMF file.
*** Reason: ASCII format is not supported in parallel, use HDF5.
*** Where: This error was encountered inside XDMFFile.cpp.
Being MPI tests I guess these failures are expected. However I wonder
how they aren't triggered when building against the autotools-built
HDF5 1.14.5 in unstable.
Full build log available on request.
Any clue?
Best,
_g.
- -- System Information:
Debian Release: 12.0
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-34-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAmliUIUACgkQ7+hsbH/+
z4OzOwf+Nw+k2gjf6KuzAQAWgra/dNcOhCID1MLYFoALZGKkLxy3+DxAXIFRySLL
lPiAcq8ErbkDnvTn+HwTYvTffxhI2PFpkKHTLL+j1KhjKcNzoYzL4KwNOM115y1w
UEWvC2P1LRmmWXKdvxO9Cjtwv4WOhNm6r3Nd944JIFzEA19elzyrdnBaj6jWK1vh
Rt2PuwRGbmHfVBUFPkAkHriWDWoZxHKq/Xwc5gZf56/fdiyVmVBifHI08vxy7IMJ
AB9kMeCaVEepQOpxQ/WdsWeJXWLMw89Hav1V4ZYYz9+LfsMfiFmbauWoL/tDJ1rw
JHmvyrT/rniP17ywA48f9YFDKi4AFA==
=awg8
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Sat, 10 Jan 2026 14:13:51 +0100 Gilles Filippini <[email protected]> wrote:
Source: dolfin
Version: 2019.2.0~legacy20240219.1c52e83-26
Severity: normal
Hi,
A test-build of dolfin against cmake-built HDF5 (1.14.6 currently in
experimental) reported extraneaous MPI test failures.
All these new failures have this message logged:
*** Error: Unable to write XDMF file.
*** Reason: ASCII format is not supported in parallel, use HDF5.
*** Where: This error was encountered inside XDMFFile.cpp.
Being MPI tests I guess these failures are expected. However I wonder
how they aren't triggered when building against the autotools-built
HDF5 1.14.5 in unstable.
Full build log available on request.
Any clue?
My bad I guess. The failures disappeared after tweaking the HDF5 helpers
to fix a FTBFS in another package.
Sorry about the noise :)
Best,
_g.
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
