Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#59433 - [openblas] Version 0.3.1-1 behaves strangely

Attached to Project: Community Packages
Opened by Bastian Beranek (totsilence) - Tuesday, 24 July 2018, 11:05 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 30 July 2018, 14:03 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I am doing numpy (python-numpy 1.14.5-1) based data analysis which is using openblas 0.3.1-1 in community testing. Numpy functions I'm using are many, for example 'np.random.poisson, np.tensordot, np.einsum, np.choose, np.where, np.repeat, ...'. It's difficult for me to share a reproducer since the code I use is rather complex.

Since todays update I'm getting wrong results out of this combination from my analysis script, which return back to normal if I downgrade openblas to 0.3.0-2.

Does numpy need to be rebuilt when openblas is updated? It doesn't seem so because openblas is only an optdepend.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 30 July 2018, 14:03 GMT
Reason for closing:  Fixed
Additional comments about closing:  openblas 0.3.2-1
Comment by Antonio Rojas (arojas) - Tuesday, 24 July 2018, 11:11 GMT
Can you check if this commit fixes your issue?

https://github.com/xianyi/OpenBLAS/commit/5f2a3c05
Comment by Bastian Beranek (totsilence) - Tuesday, 24 July 2018, 11:16 GMT
Yes, that could be it - will test. Could also be: https://github.com/xianyi/OpenBLAS/issues/1673 / https://github.com/xianyi/OpenBLAS/pull/1688
Comment by Bastian Beranek (totsilence) - Tuesday, 24 July 2018, 13:46 GMT
Hm, unless I made a mistake in compiling openblas, neither of:

https://github.com/xianyi/OpenBLAS/commit/5f2a3c05cd0e3872be3c5686b9da6b627658eeb7
https://github.com/xianyi/OpenBLAS/commit/7ba5936ecdf84a234aa2817a176e9885bb9a21f7

fixed the problem, unfortunately.
Comment by Bastian Beranek (totsilence) - Friday, 27 July 2018, 13:38 GMT
Disregard my last post, I had a typo in my test PKGBUILD. I now tried again with the latest version of the develop branch of the github repo of openblas and my code works again. I think they are going to release 0.3.2 this weekend which will hopefully fix the problem I reported here. I propose to keep this open until 0.3.2 is available in community-testing and I'll report if the issue is fixed.
Comment by Bastian Beranek (totsilence) - Monday, 30 July 2018, 09:02 GMT
openblas 0.3.2 was released this morning, when it becomes available in community-testing I'll test my script.
Comment by Felix Yan (felixonmars) - Monday, 30 July 2018, 09:11 GMT
Updated into [community-testing]. The new version fixes the numpy/scipy tests here.

Loading...