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

Percy Camilo Triveño Aucahuasi commented on ARROW-17686:
--------------------------------------------------------

Same results without errors:
{code:java}
   obj:/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
}
==3833515== LEAK SUMMARY:
==3833515==    definitely lost: 0 bytes in 0 blocks
==3833515==    indirectly lost: 0 bytes in 0 blocks
==3833515==      possibly lost: 0 bytes in 0 blocks
==3833515==    still reachable: 12,047 bytes in 194 blocks
==3833515==         suppressed: 672 bytes in 2 blocks
==3833515==
==3833515== For lists of detected and suppressed errors, rerun with: -s
==3833515== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2){code}
this time using an amd64 box (x86_64 ubuntu 22.04 with gcc toolchain)

> [C++] AsofJoinBasicParams has no gtest printer defined, leading to valgrind 
> errors
> ----------------------------------------------------------------------------------
>
>                 Key: ARROW-17686
>                 URL: https://issues.apache.org/jira/browse/ARROW-17686
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: C++
>            Reporter: Weston Pace
>            Assignee: Percy Camilo Triveño Aucahuasi
>            Priority: Major
>
> Valgrind is currently failing on arrow-compute-asof-join-node-test: 
> https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=34147&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181&l=4118
> The issue appears to be that AsofJoinBasicParams has no gtest printer and so 
> gtest is using the default universal-printer which doesn't really play well 
> with valgrind.  We should add a custom PrintTo method for AsofJoinBasicParams 
> per: 
> https://github.com/google/googletest/blob/main/googletest/include/gtest/gtest-printers.h



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to