reassing 919929 src:python-scipy 1.1.0-2 retitle 919929 python-scipy: autopkgtest fails intermittently user debian...@lists.debian.org usertags 919929 - breaks needs-update usertags 919929 flaky severity 919929 important thanks
Hi Graham, Julian, On 29-01-2019 18:59, Julian Taylor wrote: > On 29.01.19 12:01, Graham Inggs wrote: >> On 2019/01/20 21:09, Paul Gevers wrote: >> 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. That is what we call flaky behavior. >> I'm unsure what to do with this bug, perhaps re-assign to python-scipy >> only? Done so. > I am confused, scipy does not use blis. Indeed, and in the failing log one can search for "blis" and not find it at all, except for the call to autopkgtest. So the failure can't be caused by 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. Yes it is. Julian, can you please investigate the failing log files and please make the tests robust against whatever goes wrong. If you really can't fix it and still want the tests to run, consider adding the "flaky" restriction to the tests that intermittently fail. > If blis is ready enough to be used prime time, let me know we can add it > to numpy's and scipy's testsuites. No idea, and no opinion about that. Paul
signature.asc
Description: OpenPGP digital signature
