[Numpy-discussion] Using OpenBLAS for manylinux wheels
njs at pobox.com
Tue Apr 5 13:44:38 EDT 2016
On Apr 5, 2016 10:23 AM, "Matthew Brett" <matthew.brett at gmail.com> wrote:
> On Mon, Mar 28, 2016 at 2:33 PM, Matthew Brett <matthew.brett at gmail.com>
> > Hi,
> > Olivier Grisel and I are working on building and testing manylinux
> > wheels for numpy and scipy.
> > We first thought that we should use ATLAS BLAS, but Olivier found that
> > my build of these could be very slow . I set up a testing grid 
> > which found test errors for numpy and scipy using ATLAS wheels.
> > On the other hand, the same testing grid finds no errors or failures
> >  using latest OpenBLAS (0.2.17) and running tests for:
> > numpy
> > scipy
> > scikit-learn
> > numexpr
> > pandas
> > statsmodels
> > This is on the travis-ci ubuntu VMs.
> > Please do test on your own machines with something like this script :
> > source test_manylinux.sh
> > We have worried in the past about the reliability of OpenBLAS, but I
> > find these tests reassuring.
> > Are there any other tests of OpenBLAS that we should run to assure
> > ourselves that it is safe to use?
> Here is an update on progress:
> We've now done a lot of testing on the Linux OpenBLAS wheels. They
> pass all tests on Linux, with Intel kernels:
> Xianyi, the maintainer of OpenBLAS, is very helpfully running the
> OpenBLAS buildbot nightly tests with numpy and scipy:
> There is still one BLAS-related failure on these tests on AMD chips:
> I propose to hold off distributing the OpenBLAS wheels until the
> OpenBLAS tests are clean on the OpenBLAS buildbots - any objections?
Alternatively, would it make sense to add a local patch to our openblas
builds to blacklist the piledriver kernel and then distribute them now?
(I'm not immediately sure what would be involved in doing this but it seems
unlikely that it would require anything tricky?)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion