Since I updated Ubuntu from version 19.10 to 20.04 the tests umfpackamgtest, umfpackfastamgtest, umfpacktest and spqrtest are all failing due to a timeout error. The Suitesparse library is hereby the (only) Ubuntu-Repository version for Ubuntu 20.04 (and got updated together with Ubuntu from version 5.4.0 to 5.7.1).
In my concrete case this means that my code is getting compiled without error, but then it is just hanging when trying to run UMFPack and/or Cholmod (which where working perfectly fine on Ubuntu 19.10 with Suitesparse 5.4.0).
Edited
Designs
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
Yes, I even ran the attached script to make a fresh installation and run the tests in a seperate folder. It still produces the same result.test-dune-istl-master.sh
cmake does not enable any optimization by default. Perhaps there was some implicit -O flag pulled in via one of the dependencies(?!) and not anymore since the update.
If this also does not help, you should try to attach a debugger to the slow/long running process and try to find out where you are spending all the time.
I tried to reproduce this in an Ubuntu 20.04 Docker container, but the test passes (without adding any optimization flags). While discussing the issue with @simon.boisseree, he told me that umfpacktest also hangs, if run separately, so -j4 has no influence.
Without -j4 and with -O2 nothing changes and if I use gdb to debug (here I just tested umfpacktest) it hangs again and I get the attached output after pressing CTRL-C and backtracing. gdb_output.txt
I think that disabling multithreading is a workaround but not a solution. Since the real problem persists, I reopened the issue. It may also be helpful to others to have this documented, if more people run into the same problem once they update their Ubuntu distribution.
Maybe a small update: After I updated the openblas package in Ubuntu 20.04 (which was probably released a few days ago) everything works again without intel-mkl.
From my side that's totally fine, I think it was just left open because it may have affected other users who updated to Ubuntu 20.04. But now this shouldn'd be the case either way.