Your message dated Fri, 21 Aug 2026 09:12:31 +0200
with message-id <[email protected]>
and subject line Re: Bug#1125693: gemma: autopkgtest fails on ppc64el due to
numerical differences with OpenBLAS
has caused the Debian Bug report #1125693,
regarding gemma: autopkgtest fails on ppc64el due to numerical differences with
OpenBLAS
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.)
--
1125693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125693
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: openblas
Control: found -1 openblas/0.3.30+ds-3
Severity: serious
Tags: sid forky
User: [email protected]
Usertags: breaks
Control: affects -1 src:dolfin src:gemma src:openmolcas src:xtensor-blas
Dear maintainer(s),
With a recent upload of openblas the autopkgtests of dolfin, gemma,
openmolcas, and xtensor-blas fail on ppc64el in testing when their
autopkgtest is run with the binary packages of openblas from unstable.
It passes when run with only packages from testing. In tabular form (for
dolfin):
pass fail
openblas from testing 0.3.30+ds-3
dolfin from testing 2019.2.0~legacy20240219.1c52e83-24
all others from testing from testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of openblas to
testing [1]. Can you please investigate the situation?
Someone pointed me at https://github.com/OpenMathLib/OpenBLAS/pull/5463
which may completely unrelated, but at least include changes for ppc64el.
Paul
[1] https://qa.debian.org/excuses.php?package=openblas
https://ci.debian.net/data/autopkgtest/testing/ppc64el/d/dolfin/66420095/log.gz
284s Start 72: demo_singular-poisson_serial
285s 29/49 Test #72: demo_singular-poisson_serial
..............Subprocess aborted***Exception: 1.17 sec
285s terminate called after throwing an instance of 'std::runtime_error'
285s what(): 285s 285s ***
-------------------------------------------------------------------------
285s *** DOLFIN encountered an error. If you are not able to resolve
this issue
285s *** using the information listed below, you can ask for help at
285s ***
285s *** https://fenicsproject.discourse.group/
285s ***
285s *** Remember to include the error message listed below and, if
possible,
285s *** include a *minimal* running example to reproduce the error.
285s ***
285s ***
-------------------------------------------------------------------------
285s *** Error: Unable to successfully call PETSc function 'KSPSolve'.
285s *** Reason: PETSc error code is: 76 (Error in external library).
285s *** Where: This error was encountered inside
./dolfin/la/PETScKrylovSolver.cpp.
285s *** Process: 0
285s *** 285s *** DOLFIN version: 2019.2.0.64.dev0
285s *** Git changeset: debian_2019.2.0~legacy20240219.1c52e83-24
285s ***
-------------------------------------------------------------------------
285s 285s [ci-325-a328d227:14164] *** Process received signal ***
285s [ci-325-a328d227:14164] Signal: Aborted (6)
285s [ci-325-a328d227:14164] Signal code: (-6)
285s [ci-325-a328d227:14164] [ 0]
linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0) [0x3fffbb002494]
285s [ci-325-a328d227:14164] [ 1]
/lib/powerpc64le-linux-gnu/libc.so.6(+0xafd3c) [0x3fffb807fd3c]
285s [ci-325-a328d227:14164] [ 2]
/lib/powerpc64le-linux-gnu/libc.so.6(gsignal+0x2c) [0x3fffb801663c]
285s [ci-325-a328d227:14164] [ 3]
/lib/powerpc64le-linux-gnu/libc.so.6(abort+0x28) [0x3fffb7ff65f0]
285s [ci-325-a328d227:14164] [ 4]
/lib/powerpc64le-linux-gnu/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x158)
[0x3fffb83ae858]
285s [ci-325-a328d227:14164] [ 5]
/lib/powerpc64le-linux-gnu/libstdc++.so.6(+0x119ad4) [0x3fffb83a9ad4]
285s [ci-325-a328d227:14164] [ 6]
/lib/powerpc64le-linux-gnu/libstdc++.so.6(_ZSt9terminatev+0x20)
[0x3fffb835527c]
285s [ci-325-a328d227:14164] [ 7]
/lib/powerpc64le-linux-gnu/libstdc++.so.6(__cxa_throw+0x7c) [0x3fffb83a9fec]
285s [ci-325-a328d227:14164] [ 8]
/lib/powerpc64le-linux-gnu/libdolfin.so.2019.2t64(_ZNK6dolfin6Logger12dolfin_errorENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES6_S6_i+0xc1c)
[0x3fffbada1bbc]
285s [ci-325-a328d227:14164] [ 9]
/lib/powerpc64le-linux-gnu/libdolfin.so.2019.2t64(_ZN6dolfin12dolfin_errorENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_S5_z+0x184)
[0x3fffbad9e354]
285s [ci-325-a328d227:14164] [10]
/lib/powerpc64le-linux-gnu/libdolfin.so.2019.2t64(_ZN6dolfin11PETScObject11petsc_errorEiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES6_+0x370)
[0x3fffbad72cc0]
285s [ci-325-a328d227:14164] [11]
/lib/powerpc64le-linux-gnu/libdolfin.so.2019.2t64(_ZN6dolfin17PETScKrylovSolver5solveERNS_11PETScVectorERKS1_b+0x1c44)
[0x3fffbad57ad4]
285s [ci-325-a328d227:14164] [12]
/lib/powerpc64le-linux-gnu/libdolfin.so.2019.2t64(_ZN6dolfin17PETScKrylovSolver5solveERNS_13GenericVectorERKS1_+0x58)
[0x3fffbad58068]
285s [ci-325-a328d227:14164] [13]
/tmp/autopkgtest-lxc.qr0i5fy5/downtmp/build.bm6/src/dolfin-demo/documented/singular-poisson/cpp/demo_singular-poisson(+0xb5c8)
[0x13e65b5c8]
285s [ci-325-a328d227:14164] [14]
/lib/powerpc64le-linux-gnu/libc.so.6(+0x26f0c) [0x3fffb7ff6f0c]
285s [ci-325-a328d227:14164] [15]
/lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0x1ac)
[0x3fffb7ff714c]
285s [ci-325-a328d227:14164] *** End of error message ***
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,
On 14-01-2026 20:29, Paul Gevers wrote:
On 1/14/26 20:05, Sébastien Villemot wrote:
Paul: if my statement above is correct, what would be the right course
of action?
The right action would be to get those packages fixed, e.g. via filing
bugs (cloning and reassigning might be appropriate).
Somewhere between 2026-03-19 00:00:28 UTC and 2026-04-22 21:28:21 UTC
the test started to pass again in testing. Hence closing this bug report.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
