-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
Fixing "GCXS matmul => slice leads to incorrect results" #611
Conversation
Could you perhaps add a regression test, I.e. a test that would trigger the bug before and now doesn't. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #611 +/- ##
==========================================
+ Coverage 91.95% 91.97% +0.02%
==========================================
Files 20 20
Lines 3330 3340 +10
==========================================
+ Hits 3062 3072 +10
Misses 268 268 |
Please ignore the last commit. I got an unexpected Code
where |
It seems like a lot of existing tests are failing -- Would it be possible for you to look into that? |
Yes, of course, already on that. |
Hi @hameerabbasi, is it normal to have failing tests without any modification? I got 178 tests failed after simply cloning the repo. |
That's quite odd -- I'll look into it in depth this weekend, but certainly not normal. |
Did you do an editable pip install before running the tests? If not, that's normal. |
Oh yeah sorry, I fixed that. Now tests are passing. |
Actually, pre-commit.ci is failing. I don't know why! |
That can be ignored for now. |
Thanks for the fix, @EuGig! |
It fixes #607. The solution simply inverts the order of indices and of data before returning them in
_dot_csr_csr
.(I did not write any test, since I'm not implementing a new feature. Let me know if I have to do that.)