Opened 4 years ago
Closed 4 years ago
#26052 closed enhancement (fixed)
Update to OpenBLAS 0.3.3
| Reported by: | thansen | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | sage-8.5 |
| Component: | packages: standard | Keywords: | |
| Cc: | jpflori, vbraun, jdemeyer, moritz, aram.dermenjian, fbissey, embray, tscrim | Merged in: | |
| Authors: | François Bissey | Reviewers: | Erik Bray |
| Report Upstream: | N/A | Work issues: | |
| Branch: | bdf02cf (Commits, GitHub, GitLab) | Commit: | bdf02cf06a95139a09567548b5f93021413a9e12 |
| Dependencies: | Stopgaps: |
GitHub link to the corresponding issue
Description (last modified by )
OpenBLAS 0.3.2 came out and was uploaded to Debian. When attempting to build the sage 8.3 Debian package (with one thread) with this version, OpenBLAS causes a crash during the docbuild, see attached log.
A bug in OpenBLAS that involves the same error message ("OpenBLAS : Program will terminate because you tried to start too many threads.") is https://github.com/xianyi/OpenBLAS/issues/1641
Our temporary workaround for now is to use Atlas (which we already used before for architectures which are not supported by OpenBLAS).
Please consider updating OpenBLAS in sage.
Openblas 0.3.3 is now out and the threading behavior which caused many bug reports is reverted for now.
Prepared upstream tarball renamed to OpenBLAS-0.3.3.tar.gz
Attachments (1)
Change History (20)
Changed 4 years ago by
| Attachment: | sage_8.3-openblas_error.log added |
|---|
comment:1 Changed 4 years ago by
| Cc: | jpflori vbraun jdemeyer moritz aram.dermenjian added |
|---|
comment:2 Changed 4 years ago by
| Cc: | fbissey added |
|---|
comment:3 Changed 4 years ago by
comment:4 Changed 4 years ago by
I believe the problem has been addressed in 0.3.3 where they decided to switch back to the previous behavior with threads until they have fixed all the issues that have cropped in 0.3.2.
For the record I am using 0.3.3 (without openmp threads) in my own sage-on-gentoo builds.
comment:5 Changed 4 years ago by
| Authors: | → François Bissey |
|---|---|
| Branch: | → u/fbissey/openblas-0.3.3 |
| Commit: | → bdf02cf06a95139a09567548b5f93021413a9e12 |
| Description: | modified (diff) |
| Milestone: | sage-8.4 → sage-8.5 |
| Status: | new → needs_review |
| Summary: | Update to OpenBLAS 0.3.2 → Update to OpenBLAS 0.3.3 |
All the cygwin patches failed but most of the bits appears to have been merged upstream. Still someone should check cygwin with this release.
New commits:
| bdf02cf | upgrade to openblas 0.3.3
|
comment:6 Changed 4 years ago by
| Cc: | embray tscrim added |
|---|
comment:7 Changed 4 years ago by
I can confirm that the aforementioned cygwin-related patches should be safe to remove as I've had them accepted upstream for some time. I'll still want to run tests on this though. I think I can go ahead and get that started now.
comment:8 Changed 4 years ago by
I am rebasing this on 8.5.beta5 first though, though that shouldn't make too much difference.
comment:9 follow-up: 10 Changed 4 years ago by
Also I'm getting invalid checksum when I use the tarball downloaded from github...?
comment:10 Changed 4 years ago by
Replying to embray:
Also I'm getting invalid checksum when I use the tarball downloaded from github...?
could you wget the tar file and rename it? That oh so clever github API might do something more than that...
comment:11 Changed 4 years ago by
hmm, no, indeed, it seems to be wrong (and as I came here from a duplicate ticket I had for the same task, I already had my tarfile all set...) What I get is md5 30e2f8d7317e84dde5a37152173848f1
comment:12 follow-up: 15 Changed 4 years ago by
I'm not sure what you mean. That's exactly what I did. That's...disconcerting. I would hope that tarballs downloaded from GitHub wouldn't differ depending on when they were downloaded >_>
comment:15 Changed 4 years ago by
Replying to embray:
I'm not sure what you mean. That's exactly what I did. That's...disconcerting. I would hope that tarballs downloaded from GitHub wouldn't differ depending on when they were downloaded >_>
Unfortunately, it is known to happen https://github.com/cschwan/sage-on-gentoo/issues/529 . It may be that the release are not cut properly since there are repos for which I have no issues. In any case github lets you upload your own tarball prepared with sdist and the like. And people should really do it.
So someone will have to host a reference tarball until it makes it to the sage mirror.
comment:18 Changed 4 years ago by
| Description: | modified (diff) |
|---|---|
| Status: | needs_review → positive_review |
Ok added the tarball matching the checksum in the description. Since Erik says he is happy with it I am switching it to positive review.
comment:19 Changed 4 years ago by
| Branch: | u/fbissey/openblas-0.3.3 → bdf02cf06a95139a09567548b5f93021413a9e12 |
|---|---|
| Resolution: | → fixed |
| Status: | positive_review → closed |
I am not experiencing this problem in sage-on-gentoo. However I decided to only use "regular threads" and no "openmp threads" in openblas some time ago. I suspect that is why I am not affected at this stage. It may be that I have the wrong picture of threading in openblas as well.