[
https://issues.apache.org/jira/browse/ARROW-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586818#comment-16586818
]
Lukasz Bartnik edited comment on ARROW-1380 at 8/21/18 2:39 AM:
----------------------------------------------------------------
All Valgrind errors seem to originate in libpython. I re-ran:
{{export PLASMA_VALGRIND=1 }}
{{python -m pytest -vv -r sxX --durations=15 -s $PYARROW_PATH --parquet}}
with a suppression file aiming at _obj:*/libpython3.6m.so*_ (attached) and all
errors got suppressed. Another way to show it is to extract all suppressions
from Valgrind: there are no C++ related context filters among those extracted
suppressions.
was (Author: lbartnik):
All valgrind errors seem to originate in libpython. I re-ran:
{{export PLASMA_VALGRIND=1 }}
{{python -m pytest -vv -r sxX --durations=15 -s $PYARROW_PATH –parquet}}
with a suppression file aiming at _obj:*/libpython3.6m.so*_ (attached) and all
errors got suppressed. Another way to show it is to extract all suppressions
from Valgrind: there are no C++ related context filters among those extracted
suppressions.
> [C++] Fix "still reachable" valgrind warnings in Plasma Python unit tests
> -------------------------------------------------------------------------
>
> Key: ARROW-1380
> URL: https://issues.apache.org/jira/browse/ARROW-1380
> Project: Apache Arrow
> Issue Type: Bug
> Components: Plasma (C++)
> Reporter: Wes McKinney
> Priority: Major
> Fix For: 0.11.0
>
> Attachments: LastTest.log, valgrind.supp_
>
>
> I thought I fixed this, but they seem to have recurred:
> https://travis-ci.org/apache/arrow/jobs/266421430#L5220
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
