I have reproduced the issue on the infrastructure. This seems to be related to pthread support in openblas, as if I swap it out for openblas' openmp variant, it works.
Now there have been no changes in openblas aside from restructuring the packaging, so the real cause must surely lie elsewhere - maybe it picked up a newer pthread symbol version from libc, or an inline function from liblapack? It does not hang - it seems to be stuck in an infinite loops - all 4 processes run at 400% CPU usage, and seem busy locking and unlocking a mutex. I also rebuilt openblas on the autopkgtest host (w/o proposed) and tested with that, but the failure is the same. I don't think it's worthwhile exploring this further - users can switch to the openmp variant of openblas if they encounter issues in the pthread one, and who uses this on armhf anyway? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860601 Title: openblas: causes autopkgtest failure in hypre armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hypre/+bug/1860601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
