Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in single threaded positive definite inverse in OpenBLAS #126

Closed
andreasnoack opened this issue Jul 10, 2014 · 21 comments
Closed

Error in single threaded positive definite inverse in OpenBLAS #126

andreasnoack opened this issue Jul 10, 2014 · 21 comments
Labels
bug Something isn't working upstream The issue is with an upstream dependency, e.g. LLVM

Comments

@andreasnoack
Copy link
Member

As reported at the list

Issue filed: OpenMathLib/OpenBLAS#410

@ViralBShah
Copy link
Member

We need to have this fix in 0.3, and it seems likely that the fix will be part of openblas 0.2.10.

Cc: @xianyi @wernsaar

@tkelman
Copy link

tkelman commented Jul 10, 2014

the linalg tests are already really long, but could any additional tests have caught the difference between single and multi threaded openblas here?

@andreasnoack
Copy link
Member Author

I think, it only happened for large matrices, so we can just set n=1000 instead of n=10😃

@mlubin
Copy link
Member

mlubin commented Jul 10, 2014

It seems like the linalg tests are becoming mostly a unit test suite for OpenBLAS.

@tkelman
Copy link

tkelman commented Jul 10, 2014

Yeah, largely. Their own tests are more comprehensive than ours, but Julia gets installed on a wider variety of machines than the OpenBLAS devs have access to.

@ViralBShah
Copy link
Member

Maybe we should have a small set of tests that are run with different problem sizes and with different numbers of threads.

@tkelman
Copy link

tkelman commented Jul 16, 2014

OpenBLAS 0.2.10 is out with the fix for this, time for another bump?

@ViralBShah
Copy link
Member

Could you test it out and bump it? I am just boarding a flight to India and will be mostly in an aluminium tube for the next 30 hours or so.

@tkelman
Copy link

tkelman commented Jul 16, 2014

Hm, judging by OpenMathLib/OpenBLAS#415 there may be trouble on 32 bit Linux?

@ViralBShah
Copy link
Member

Looks like it has been fixed and there is a new 0.2.10 tag.

@staticfloat
Copy link
Member

I'm currently testing out 0.2.10 on Ubuntu and OSX. I will submit a PR when I've finished.

@ViralBShah
Copy link
Member

@staticfloat Did this work out?

@staticfloat
Copy link
Member

Through my adventures, we've gotten a re-tagged 0.2.10 (along with a promise from the devs that they'll try to just release new versions instead of retagging). PR is here, but it would be nice if someone could verify that the issue reported in this thread is actually solved by version bump.

@ViralBShah
Copy link
Member

I just merged it, thinking from the comments in the PR that it was good to go. Anyways, I am building right now and will speak up if it fails.

@tkelman
Copy link

tkelman commented Jul 18, 2014

I reproduced this problem in a pre-0.2.10 version and saw it fixed in the first tagged version of 0.2.10, which differed only in a single line from the second tag, so I think we're okay

@ViralBShah
Copy link
Member

I don't see the PosDef exception any more.

@ViralBShah
Copy link
Member

I wonder if we can print a line in the banner encouraging everyone who downloads julia to run the tests during the RC stage and report issues.

@tkelman
Copy link

tkelman commented Jul 19, 2014

Why just during the RC stage? Should put it on the download page. Julia is under heavy development, here's how to run the test suite first thing after installing a binary, if it doesn't pass then search github for similar issues and add a comment if you see something that's already been reported, or open a new issue if you can't find anything similar.

@ViralBShah
Copy link
Member

That is a valid point, and I actually like the idea. The downloads page can have detailed instructions, and the banner can have something just as a reminder. Perhaps the request to run tests can be made quiet after the tests are run for that particular version.

@ivarne
Copy link
Member

ivarne commented Jul 20, 2014

Maybe a not tested/tested/test failure notice in yellow/green/red?

@ViralBShah
Copy link
Member

Great idea! Perhaps we should have a new issue for this.

@KristofferC KristofferC transferred this issue from JuliaLang/julia Nov 26, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream The issue is with an upstream dependency, e.g. LLVM
Projects
None yet
Development

No branches or pull requests

6 participants