Evgeni Burovski
Evgeni Burovski
What are the inputs to the lstsq routine, X and y? You can add a `breakpoint()`, step through and print the inputs and their shapes.
If this persists for a clean reinstall (you don't need scikit-learn, just numpy and scipy), I'd 1) step through `lstsq` in pdb to make sure the arrays are what I...
One trick is to add pair of breakpoints: a python one + a C breakpoint: ``` $ cat lstsq_repro.py import numpy as np from scipy.linalg import lstsq a = np.eye(2,...
Step through the python code of lstsq, find which python line fails. From it, find the corresponding C symbol and add a gdb breakpoint on it. It might be that...
The point is, RISC-V is currently supported on a best-effort basis. Meaning, we are happy to accept patches which do not break our supported set of platforms (e.g., do not...
Looks like this issue has run its course thanks to gh-17322. Or is there anything to keep this issue open @melissawm ?
gh-20335 removed xfails and bumped tolerances where needed for the tests to pass on our CI. Closing. Thanks all.
Closing then. Thanks @thalassemia
A slight git glitch here --- this PR probably needs something like ` git rebase 8a99fae` (the last extra commit) or ` git rebase upstream/main`, followed by a force-push.
Stumbled on this while trying to figure out why the cupy main does not build on a machine it did in December. Tracked it down to cusparseLT 0.5.2 installed on...