Marius Bakke writes: >> Without OpenBLAS dlib will use an internal BLAS implementation. I'm >> fairly certain that will at least fix the crash on x86_64, which was >> a segfault in libopenblasp-r0.2.15.so when we had LAPACK in inputs, but >> seems to consistently trigger on Hydra regardless. >> >> I got busy this weekend, but will try to reproduce the i686 errors this >> week; and also check if the newer openblas in core-updates solves the >> x86_64 segfault. >> >> Stay tuned... > > Short update: I can successfully reproduce the i686 test failures simply > by `guix build --system=i686-linux` on x86_64. Removing OpenBLAS from > inputs had no effect. Now to figure out what's going on.. There are a couple of things going on in this thread: 1. Segfault on x86_64. This seems to have been resolved simply by updating OpenBLAS. At least, I'm no longer able to reproduce it even with LAPACK in inputs. So, that should fix the Hydra x86_64 build. Can the OpenBLAS update be cherry-picked to master? 2. i686 test failures. Updating OpenBLAS fixed 1/5 errors. The remaining four are reproducible on 32-bit Ubuntu, so they do not seem Guix related. Upstream has been notified. 3. ARM failures. I don't have ARM hardware to test on, but I'm guessing it's similar to i686 (i.e. not directly Guix related). Adding "#:parallel-build? #f" had no effect on tests, indeed the check phase does not seem to use the previously built dlib; it builds it again without parallel-build. I will try reproducing the non-reproducibility on some higher end hardware, hopefully this week. I've also found that FFTW is no longer used, apparently due to thread safety issues. So I'd appreciate if the following patch can be added. Apologies for not catching the missing reference earlier, I will be more careful in the future (fftw was added in the last minute..).