Comment 0 for bug 1860601

openblas >= 0.3.7+ds-3 causes an autopkgtest regression in hypre on armhf on Ubuntu infrastructure.

There was a major restructuring of the openblas packaging in Debian version 0.3.7+ds-2 uploaded to experimental.

http://autopkgtest.ubuntu.com/packages/h/hypre/focal/armhf

Running tests
running TEST_ams ... autopkgtest [17:08:06]: ERROR: timed out on command

I have tried to reproduce this error on a Debian porterbox (armhf chroot on arm64 kernel) and on a Raspberry Pi 3 (armhf focal-proposed chroot on focal arm64 kernel). The autopkgtests using binaries from the archive are successful, and rebuilding the packages locally is fine too.

While investigating, I found the same tests are run while building the hypre package.
I uploaded the hypre package to my PPA with the following change:

--- a/debian/control
+++ b/debian/control
@@ -10,8 +10,8 @@
  debhelper-compat (= 12),
  pkg-config,
  gfortran,
- libblas-dev | libopenblas-dev | libatlas-base-dev | libblas.so,
- liblapack-dev | libopenblas-dev | libatlas-base-dev | liblapack.so,
+ libopenblas-dev | libblas-dev | libatlas-base-dev | libblas.so,
+ libopenblas-dev | liblapack-dev | libatlas-base-dev | liblapack.so,
  libsuperlu-dev, libsuperlu-dist-dev,
  libltdl-dev,
  libtool,

i.e. building the package with libopenblas-dev instead of libblas-dev and liblapack-dev.

https://launchpad.net/~ginggs/+archive/ubuntu/testing/+sourcepub/10932575/+listing-archive-extra

The builds across all architectures seemed to fail in the same way as the autopkgtests on armhf.
TEST_ams would start, and eventually the build would time out.

see e.g. the build log for amd64:

https://launchpad.net/~ginggs/+archive/ubuntu/testing/+build/18567417/+files/buildlog_ubuntu-focal-amd64.hypre_2.18.2-1~ppa2_BUILDING.txt.gz

Again, I was unable to reproduce this error locally on amd64 or armhf.

This regression prevents openblas, yade, eckit, sdpa, openmolcas and bolt-lmm from migrating from -proposed.