You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Uwe L. Korn (JIRA)" <ji...@apache.org> on 2017/06/19 10:48:00 UTC

[jira] [Commented] (ARROW-1127) pyarrow 4.1 import failure on Travis

    [ https://issues.apache.org/jira/browse/ARROW-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053776#comment-16053776 ] 

Uwe L. Korn commented on ARROW-1127:
------------------------------------

That time corresponds roughly to when I updated the jemalloc feedstock on conda-forge. Maybe we need to rebuilt {{pyarrow}} or change the package to link against jemalloc 4.x ([~jreback] can you test if pinning jemalloc to 4.4.0 fixes the issue?)

The actual problem here is caused by a bug in glibc (see fix here: https://www.sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=67cbf9a2a9e8953aa7ea875938d6646727c71aaa). Thus possibly doesn't appear on OSX as there is a different glibc version.

> pyarrow 4.1 import failure on Travis
> ------------------------------------
>
>                 Key: ARROW-1127
>                 URL: https://issues.apache.org/jira/browse/ARROW-1127
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Python
>    Affects Versions: 0.4.1
>            Reporter: Jeff Reback
>
> Our last pandas good run was 3 days ago, Failures started 15 hours ago (https://travis-ci.org/pandas-dev/pandas/jobs/244286287). 
> Here pyarrow (0.4.1) is a dep of feather (0.4.0)
> The failure *only* appears to be on unix (works ok on macosx).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)