Opened 14 months ago

Last modified 14 months ago

#52559 new defect

py27-numpy fresh installation on Sierra fails test

Reported by: shigemi.ohta@… Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc:
Port: py27-numpy

Description (last modified by larryv (Lawrence Velázquez))

numpy.test('full') quickly fails:

FAIL: test_refcount_vdot (test_regression.TestRegression)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/tests/test_regression.py", line 659, in test_refcount_vdot
    _assert_valid_refcount(np.vdot)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/testing/utils.py", line 1336, in _assert_valid_refcount
    assert_(sys.getrefcount(i) >= rc)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/testing/utils.py", line 75, in assert_
    raise AssertionError(smsg)
AssertionError

----------------------------------------------------------------------
Ran 5940 tests in 1441.503s

FAILED (KNOWNFAIL=6, SKIP=30, failures=1)

Change History (7)

comment:1 follow-up: Changed 14 months ago by larryv (Lawrence Velázquez)

  • Description modified (diff)
  • Owner changed from macports-tickets@… to michaelld@…
  • Port py27-numpy added

Thanks for the report. Please Cc port maintainers in the future:

$ port info --maintainers py27-numpy

comment:2 in reply to: ↑ 1 Changed 14 months ago by shigemi.ohta@…

Replying to larryv@…:

Thanks for the report. Please Cc port maintainers in the future:

$ port info --maintainers py27-numpy

Thank you. The original failure was on my MacBook Pro newly running on Sierra. Now I found the same failure occurs with my office iMac, also newly on Sierra. In addition, on the latter, scipy.test('full') fails rather quickly too. Shall I open another ticket for that?

comment:3 Changed 14 months ago by michaelld (Michael Dickens)

Please just keep everything on this ticket since they are directly related.

comment:4 follow-up: Changed 14 months ago by michaelld (Michael Dickens)

a few thoughts / personal opinions:

  • I'm glad you reported this issue, and please don't take my comments here personally or as flippant.
  • if NumPy otherwise works for your needs, then that's what matters. If NumPy is failing in some critical way, then please report the issue both here and to the NumPy folks themselves. The issue might be with MacPorts, or it might be with NumPy.
  • Given that this is a runtime issue, I'd advise you -- if you're adamant about this part of NumPy working -- to take the issue upstream to the NumPy folks themselves. Quite honestly, these sorts of issues are a bit beyond us port maintainers' "pay grade". Most of us port maintainers are doing MacPorts work pro-bono (for free), so we get to what we can when we can.
  • We welcome patches! If you feel compelled to hack on NumPy to fix these or other issues, please do so & attach a patch to this ticket & a comment about the fix. Again, nothing personal; we do the best we can.

comment:5 in reply to: ↑ 4 Changed 14 months ago by shigemi.ohta@…

Thank you. No, I am not adamant about f2py, or fortran, but am annoyed because this prevents other tests. I would be willing to bring this to upstream, but am not sure how to: I would appreciate if you could tell me how. Also, can you try the newer 1.11.2?

Replying to michaelld@…:

a few thoughts / personal opinions:

  • I'm glad you reported this issue, and please don't take my comments here personally or as flippant.
  • if NumPy otherwise works for your needs, then that's what matters. If NumPy is failing in some critical way, then please report the issue both here and to the NumPy folks themselves. The issue might be with MacPorts, or it might be with NumPy.
  • Given that this is a runtime issue, I'd advise you -- if you're adamant about this part of NumPy working -- to take the issue upstream to the NumPy folks themselves. Quite honestly, these sorts of issues are a bit beyond us port maintainers' "pay grade". Most of us port maintainers are doing MacPorts work pro-bono (for free), so we get to what we can when we can.
  • We welcome patches! If you feel compelled to hack on NumPy to fix these or other issues, please do so & attach a patch to this ticket & a comment about the fix. Again, nothing personal; we do the best we can.

comment:6 follow-up: Changed 14 months ago by michaelld (Michael Dickens)

I just pushed 1.11.2 in r153815. It won't fix the f2py issue; it might address the other issue.

comment:7 in reply to: ↑ 6 Changed 14 months ago by shigemi.ohta@…

I joined numpy-discussion@… and reported the issue there at Wed, 12 Oct 2016 23:08:44 +0900. No direct response, but today I ran "port upgrade outdated" on my office iMac that resulted in updating dbus, gcc6, glib2, hdf5, sqlite3, ImageMagick, jasper, netcdf, py27-setuptools, poppler, py27-numpy, snappy, and texlive-bin. After this upgrade "numpy.test()," "scipy.test()," and "scipy.test('full')" all pass without an unknown failure, while numpy.test('full') still fails the same way with f2py. The situation appears the same on my own MacBook Pro. So I am satisfied now. Thank you very much.

Replying to michaelld@…:

I just pushed 1.11.2 in r153815. It won't fix the f2py issue; it might address the other issue.

Last edited 14 months ago by shigemi.ohta@… (previous) (diff)
Note: See TracTickets for help on using tickets.