Bug 204183 - [MAINTAINER] math/py-pandas: Update to 0.17.0
Summary: [MAINTAINER] math/py-pandas: Update to 0.17.0
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Wen Heping
URL:
Keywords: easy, patch, patch-ready
Depends on:
Blocks:
 
Reported: 2015-10-31 23:22 UTC by John W. O'Brien
Modified: 2015-11-01 16:05 UTC (History)
2 users (show)

See Also:


Attachments
Update math/py-pandas to 0.17.0 (854 bytes, patch)
2015-10-31 23:22 UTC, John W. O'Brien
koobs: maintainer-approval+
Details | Diff
math/py-pandas: portlint output (160 bytes, text/plain)
2015-10-31 23:22 UTC, John W. O'Brien
no flags Details
poudriere testport log for py27-pandas-0.17.0 (452.50 KB, text/plain)
2015-10-31 23:23 UTC, John W. O'Brien
no flags Details
poudriere testport log for py34-pandas-0.17.0 (457.67 KB, text/plain)
2015-10-31 23:23 UTC, John W. O'Brien
no flags Details
Nosetests output (w/python2.7 and all options enabled) (746.78 KB, text/plain)
2015-10-31 23:24 UTC, John W. O'Brien
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description John W. O'Brien 2015-10-31 23:22:16 UTC
Created attachment 162654 [details]
Update math/py-pandas to 0.17.0

Changelog
=========

*   Update to 0.17.0

QA
==

*   portlint

    See attached.

*   nosetests

    Ran 9043 tests in 1429.402s

    FAILED (SKIP=269, errors=2, failures=1)

    See attached for details.


ERROR: test_pytables_native_read (pandas.io.tests.test_pytables.TestHDFStore)
ERROR: test_to_hdf_with_object_column_names (pandas.io.tests.test_pytables.TestHDFStore)

I believe these are errors in devel/py-tables.


FAIL: test_sum (pandas.tests.test_panel4d.TestPanel4d)

I have reported this upstream (https://github.com/pydata/pandas/issues/11495).
Comment 1 John W. O'Brien 2015-10-31 23:22:40 UTC
Created attachment 162655 [details]
math/py-pandas: portlint output
Comment 2 John W. O'Brien 2015-10-31 23:23:22 UTC
Created attachment 162656 [details]
poudriere testport log for py27-pandas-0.17.0
Comment 3 John W. O'Brien 2015-10-31 23:23:45 UTC
Created attachment 162657 [details]
poudriere testport log for py34-pandas-0.17.0
Comment 4 John W. O'Brien 2015-10-31 23:24:09 UTC
Created attachment 162658 [details]
Nosetests output (w/python2.7 and all options enabled)
Comment 5 Kubilay Kocak freebsd_committer freebsd_triage 2015-11-01 04:19:39 UTC
@John Given the consistency and quality of your contributions to date, please feel free to just confirm that your changes pass QA in your initial issue description, without needing to attach logs. Something like the following is fine:

 * portlint: OK|WARN: output
 * testport: OK (poudriere, versions, archs, combinations tested)
 * unittest: OK (Ran 9043 tests in 1429.402s FAILED (SKIP=269, errors=2, failures=1)

Don't forget to also set maintainer-approval on the attachments you want committers to address. You can mouse over the name of any flag to see what each of the values mean.
Comment 6 commit-hook freebsd_committer freebsd_triage 2015-11-01 13:13:00 UTC
A commit references this bug:

Author: wen
Date: Sun Nov  1 13:12:40 UTC 2015
New revision: 400611
URL: https://svnweb.freebsd.org/changeset/ports/400611

Log:
  - Update to 0.17.0

  PR:		204183
  Submitted by:	john@saltant.com(maintainer)

Changes:
  head/math/py-pandas/Makefile
  head/math/py-pandas/distinfo
Comment 7 John W. O'Brien 2015-11-01 13:53:41 UTC
@koobs:
> Given the consistency and quality of your contributions to date, please feel
> free to just confirm that your changes pass QA in your initial issue
> description, without needing to attach logs.

Got it. Thank you.

> Don't forget to also set maintainer-approval on the attachments you want
> committers to address.

This confuses me. Submitting as the maintainer, isn't my approval of my own patch implied?

@wen: Thank you for committing!
Comment 8 Kubilay Kocak freebsd_committer freebsd_triage 2015-11-01 16:05:19 UTC
(In reply to John W. O'Brien from comment #7)

It is implied, but searches cant be made on that because the concept of a maintainer is in the ports tree, but not bugzilla, hence the flag.

Explicitly setting it results in the issue showing up in reports and saved searches that committers look at.