-
Notifications
You must be signed in to change notification settings - Fork 21
spin 0.9 update causes AttributeError in numpy CI #193
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
Comments
I can replicate with a conda install. |
This error breaks numpy builds in a particularly confusing way. It doesn't help that Googling the error message doesn't lead to this issue for some reason (I guess Google doesn't actually index the web anymore). Is it possible for spin to output a traceback in cases like this? Perhaps whatever code is hiding the tracebacks could try to detect if the error is a spin internal error and unhide it in that case. To be clear if anyone does manage to find this issue, downgrading to spin=0.8 fixes the issue. |
Thanks, Aaron, I think that'd be a good feature to add. NumPy CI is pinned to the hash which works, but we should get 0.9.1 out the door. |
See PR #198 |
It looks like this broke one of the numpy CI jobs: https://github.com/numpy/numpy/actions/runs/9087080853/job/24974107681?pr=26436
And indeed there's a new access of a
dir_info
attribute added in #155.Clues about how to fix this in the numpy CI would be appreciated if this isn't a spin bug.
The text was updated successfully, but these errors were encountered: