WillAyd commented on PR #258:
URL: https://github.com/apache/arrow-nanoarrow/pull/258#issuecomment-1639059847

   Any idea what I might be overlooking with the tests and how they allocate 
memory? Locally I get this valgrind traceback:
   
   ```sh
   ==710574==    at 0x4843828: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
   ==710574==    by 0x1C6BFD: ArrowMalloc (utils.c:194)
   ==710574==    by 0x1BF55A: ArrowArrayInitFromType (array.c:139)
   ==710574==    by 0x143D36: 
ArrayTest_ArrayTestAppendToIntervalArrayMonthDayNano_Test::TestBody() 
(array_test.cc:934)
   ==710574==    by 0x2048CA: void 
testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, 
void>(testing::Test*, void (testing::Test::*)(), char const*) (gtest.cc:2607)
   ==710574==    by 0x1FC940: void 
testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, 
void>(testing::Test*, void (testing::Test::*)(), char const*) (gtest.cc:2643)
   ==710574==    by 0x1D002F: testing::Test::Run() (gtest.cc:2682)
   ==710574==    by 0x1D0AFD: testing::TestInfo::Run() (gtest.cc:2861)
   ==710574==    by 0x1D1426: testing::TestSuite::Run() (gtest.cc:3015)
   ==710574==    by 0x1E13F4: testing::internal::UnitTestImpl::RunAllTests() 
(gtest.cc:5855)
   ==710574==    by 0x2058C9: bool 
testing::internal::HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl,
 bool>(testing::internal::UnitTestImpl*, bool 
(testing::internal::UnitTestImpl::*)(), char const*) (gtest.cc:2607)
   ==710574==    by 0x1FDAD2: bool 
testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl,
 bool>(testing::internal::UnitTestImpl*, bool 
(testing::internal::UnitTestImpl::*)(), char const*) (gtest.cc:2643)
   ```
   
   Not immediately clear what is different from the other tests in terms of 
building the array


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to