Bug#919929: blis breaks python-scipy autopkgtest

Julian Taylor jtaylor.debian at googlemail.com
Tue Jan 29 17:59:37 GMT 2019


On 29.01.19 12:01, Graham Inggs wrote:
> Hi Paul
> 
> On 2019/01/20 21:09, Paul Gevers wrote:
>> With a recent upload of blis the autopkgtest of python-scipy fails in
>> testing when that autopkgtest is run with the binary packages of blis
>> from unstable. It passes when run with only packages from testing. In
>> tabular form:
>>                         pass            fail
>> blis                   from testing    0.5.1-5
>> python-scipy           from testing    1.1.0-2
>> all others             from testing    from testing
> 
> From testing's test logs [1], python-scipy 1.1.0-2 passed with
> blis/0.5.1-5 on 2019-01-21 05:22:48 UTC.  It then passed with
> blis/0.5.1-6 and blis/0.5.1-7, but failed with blis/0.5.1-7 on
> 2019-01-27 17:55:32 UTC.
> 
> From unstable's test logs [2], python-scipy 1.1.0-2 seems to have many
> intermittent failures since 2018-12-02.
> 
> I'm unsure what to do with this bug, perhaps re-assign to python-scipy
> only?

I am confused, scipy does not use blis.
It tests libblas, openblas and atlas but blis was so far I know never
configured as a blas source in the tests.
Unless something has changed with those packages that they pull blis
this might be a false positive.

If blis is ready enough to be used prime time, let me know we can add it
to numpy's and scipy's testsuites.



More information about the debian-science-maintainers mailing list