Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#49747 closed update (fixed)

py-pymc: update to 2.3.6, correct GitHub PortGroup add gcc5 (as default) and py35 variants

Reported by: Russell-Jones-OxPhys (Russell Jones) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: haspatch Cc: humem (humem), majoc-at-astro (majoc-at-astro), kurthindenburg (Kurt Hindenburg)
Port: py-pymc

Description

Portfile and diff attached.

All tests pass in python 3.4 and 3.5 (well, it "fails" with a set of DeprecationWarnings, but I think that's not a problem-- or at least one to be fixed upstream), but one fails in 2.7 as below.

I'll check if the 2.7 failure is an upstream bug. I'm also rebuilding py27-numpy and scipy gcc5 to see if that's the cause. Perhaps this should be enforced or warned about by the port if it is the problem?

FAIL: test_consistency (pymc.tests.test_distributions.test_skew_normal)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pymc/tests/test_distributions.py", line 1075, in test_consistency
    assert_array_almost_equal(hist, like, 1)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/testing/utils.py", line 886, in assert_array_almost_equal
    precision=decimal)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/testing/utils.py", line 708, in assert_array_compare
    raise AssertionError(msg)
AssertionError: 
Arrays are not almost equal to 1 decimals

(mismatch 10.0%)
 x: array([ 0. ,  0. ,  0.1,  0.3,  0.6,  1. ,  1.7,  2.1,  1.9,  0.3])
 y: array([ 0. ,  0. ,  0.1,  0.3,  0.6,  1.1,  1.7,  2.2,  1.7,  0.3])

(The 3.5 deprecation warnings are all as below)

DeprecationWarning (inspect.getargspec() is deprecated, use inspect.signature() instead)

Attachments (2)

Portfile-py-pymc.diff (993 bytes) - added by Russell-Jones-OxPhys (Russell Jones) 8 years ago.
Portfile-py-pymc (4.2 KB) - added by Russell-Jones-OxPhys (Russell Jones) 8 years ago.

Download all attachments as: .zip

Change History (8)

Changed 8 years ago by Russell-Jones-OxPhys (Russell Jones)

Attachment: Portfile-py-pymc.diff added

Changed 8 years ago by Russell-Jones-OxPhys (Russell Jones)

Attachment: Portfile-py-pymc added

comment:1 Changed 8 years ago by Russell-Jones-OxPhys (Russell Jones)

Yes, using +gcc5 for numpy, scipy and py-pymc prevents the test failure.

comment:2 Changed 8 years ago by majoc-at-astro (majoc-at-astro)

Cc: majoc@… added

Cc Me!

comment:3 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)

Keywords: haspatch added
Summary: Update py-pymc to 2.3.6, correct GitHub PortGroup add gcc5 (as default) and py35 variantspy-pymc: update to 2.3.6, correct GitHub PortGroup add gcc5 (as default) and py35 variants

A sha256 checksum should be used as well. Each distfile should be verified by more than one checksum algorithm.

comment:4 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)

Cc: khindenburg@… added

Cc Me!

comment:5 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)

Resolution: fixed
Status: newclosed

done r144126

comment:6 Changed 8 years ago by dstrubbe (David Strubbe)

How did you run these tests? This port should have a test phase enabled.

Note: See TracTickets for help on using tickets.