TST: Tests failed with Numpy DeprecationWarning about np.broadcast_arrays
See original GitHub issueExample log from master
from the numpy-dev
job: https://api.travis-ci.org/v3/job/552167685/log.txt
DeprecationWarning: Numpy has detected that you (may be) writing to an array with
overlapping memory from np.broadcast_arrays. If this is intentional
set the WRITEABLE flag True or make a copy immediately before writing.
215 failures total
xref numpy/numpy#12609
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
numpy.broadcast_arrays — NumPy v1.24 Manual
Deprecated since version 1.17: The output is currently marked so that if written to, a deprecation warning will be emitted. A future version...
Read more >Python: DeprecationWarning: elementwise == comparison ...
I assume the error occurs in this expression: np.sum(np.argmax(predictions, 1) == np.argmax(labels, 1)). can you tell us something about the ...
Read more >NumPy 1.13.0 Release Notes
np.isnat ufunc tests for NaT special datetime and timedelta values¶ ... all uncaught warnings will now be considered a test failure.
Read more >Release Notes — NumPy v1.12 Manual - GitHub Pages
Due to the change in implementation some very delicate tests may fail ... np.array(2)/np.array(3)" -c:1: DeprecationWarning: numpy: classic int division ...
Read more >Numerical Python - Browse /NumPy/1.10.2 at SourceForge.net
gh-6556 BUG: Error in broadcast_arrays with as_strided array. * gh-6558 MAINT: Minor update to "make ... gh-6698 TST: test np.rint bug for large...
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
Looking into this more, I’ve concluded it is really an upstream issue: https://github.com/numpy/numpy/issues/13929
@pllim - this warning was meant to show only when we are actually trying to write to a broadcast array - which we should never do. So, I think we should only look at the actual cases where the warning is given.
From the log file, it looks like there is only a single problem somewhere in the
LombScargle
implementation, which we probably can fix by looking carefully at that code.