![](https://secure.gravatar.com/avatar/aee56554ec30edfd680e1c937ed4e54d.jpg?s=120&d=mm&r=g)
I just tested those new openblas-based wheels on the linux virtualbox setup that I used to report the following segfault back in February: https://mail.scipy.org/pipermail/numpy-discussion/2016-February/074866.html https://mail.scipy.org/pipermail/numpy-discussion/2016-February/074870.html I cannot reproduce this problem anymore with this new version of OpenBLAS. All scikit-learn tests pass (I had originally encountered the segfault when runing the scikit-learn tests). I also ran the numpy and scipy tests successfully on that machine. What I find reassuring is that the upstream OpenBLAS has set up a buildbot based CI to test OpenBLAS on many CPU architectures and is running the scipy test continuously to detect regressions early on: https://github.com/xianyi/OpenBLAS/issues/785 http://build.openblas.net/waterfall https://github.com/xianyi/OpenBLAS-CI/ -- Olivier Grisel