Zha0q1 opened a new pull request #19008:
URL: https://github.com/apache/incubator-mxnet/pull/19008


   fixes https://github.com/apache/incubator-mxnet/issues/19006
   
   Now this can run
   ``` python
   import mxnet
   from mxnet import np, npx
   INT_OVERFLOW = 2**31
   A = np.array([INT_OVERFLOW])
   assert A == INT_OVERFLOW
   assert INT_OVERFLOW == A
   ```
   
   I also unskipped a test which will pass now give this fix.
   
   local run:
   
   ```
   ubuntu@ip-172-31-38-169:~/incubator-mxnet$ pytest 
tests/nightly/test_np_large_array.py::test_shape_array
   /home/ubuntu/anaconda3/lib/python3.7/importlib/_bootstrap.py:219: 
RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. 
Expected 192 from C header, got 216 from PyObject
     return f(*args, **kwds)
   /home/ubuntu/anaconda3/lib/python3.7/importlib/_bootstrap.py:219: 
RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. 
Expected 192 from C header, got 216 from PyObject
     return f(*args, **kwds)
   /home/ubuntu/anaconda3/lib/python3.7/importlib/_bootstrap.py:219: 
RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. 
Expected 192 from C header, got 216 from PyObject
     return f(*args, **kwds)
   ==================================== test session starts 
=====================================
   platform linux -- Python 3.7.7, pytest-5.4.1, py-1.8.1, pluggy-0.13.1
   rootdir: /home/ubuntu/incubator-mxnet, inifile: pytest.ini
   plugins: remotedata-0.3.2, openfiles-0.4.0, astropy-header-0.1.2, 
hypothesis-5.8.3, arraydiff-0.3, doctestplus-0.5.0
   collected 1 item                                                             
                
   
   tests/nightly/test_np_large_array.py .                                       
          [100%]
   
   ===================================== 1 passed in 3.64s 
======================================
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to