TST: 191 failures with numpy-dev
See original GitHub issueFailures are in coordinates
, io.ascii
, table
, and utils.iers
. Error is AttributeError: 'MaskedArray' object has no attribute 'info'
Example log from weekly cron: https://github.com/astropy/astropy/runs/7383859498?check_suite_focus=true
I also restarted a previously passing dev job in main
and it fails now: https://github.com/astropy/astropy/runs/7390810435?check_suite_focus=true
@seberg thinks it is caused by https://github.com/numpy/numpy/pull/21977 (see https://github.com/numpy/numpy/pull/21999#issuecomment-1187672181)
@mhvk , hope you can advise!
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
numpy.core._multiarray_umath failed to import · Issue #11871
I re-installed everything and had the same problem, so I just created a test venv with only numpy and tensorflow; importing tensorflow works....
Read more >python - scikit-learn install failure / numpy not found / missing ...
Ok when i installed numpy with pip or normally all the include header were missing. To fix this i installed the package "python-numpy-devel"...
Read more >Troubleshooting ImportError — NumPy v1.25.dev0 Manual
Importing the numpy c-extensions failed. This error can happen for different reasons, often due to issues with your setup.
Read more >Chapter 4. NumPy Basics: Arrays and Vectorized Computation
If casting were to fail for some reason (like a string that cannot be converted to float64 ), a TypeError will be raised....
Read more >GitLab CI Dependency Scanning fails with numpy (#103477)
When using Dependency Scanning template with python and the package numpy, it will exit with error code 1 due to ModuleNotFoundError: No ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sounds like the plan is to revert, in which case this can come later. Which is good, since I don’t really have much time right now…
Quite a number of the failures will need an upstream fix. I do not think this will get rid of everything but from the quick look I had, it should not be difficult to ensure we can work with an updated change.