Arkur745 commented on PR #47522:
URL: https://github.com/apache/arrow/pull/47522#issuecomment-3265844608

   > Could you fix lint failures? You can enable GitHub Actions on your fork to 
check CI results on your fork.
   
   @kou, I am having the entire project and all the tests compile successfully. 
The final build log confirms that arrow-array-test.exe is being created 
correctly. 
   However, when I run the test executable directly, the Google Test runner 
reports that it found 0 tests, even though the code contains the new 
TestStructBuilder test suite.
   
   
   `C:\dev\arrow\cpp\build\debug\Debug\arrow-array-test.exe 
--gtest_filter=*TestStructBuilder*
   
   Running main() from 
C:\dev\arrow\cpp\build\_deps\googletest-src\googletest\src\gtest_main.cc
   
   Note: Google Test filter = *TestStructBuilder*
   
   [==========] Running 0 tests from 0 test suites.
   
   [==========] 0 tests from 0 test suites ran. (2 ms total)
   [  PASSED  ] 0 tests.`
   
   The core of the issue is that the build system doesn't seem to be 
automatically discovering the tests in array_struct_test.cc.
   I found a workaround. By manually adding this line to 
cpp/src/arrow/array/CMakeLists.txt:
   add_arrow_test(array_struct_test)
   `C:\dev\arrow\cpp\build> ctest -C Debug -R arrow-array-struct-test
   Test project 
   C:/dev/arrow/cpp/build
   Start 17: arrow-array-struct-test
   1/1 Test #17: arrow-array-struct-test ..........   Passed   2.98 sec`
   
   While my specific test passes, I've discovered that my change to the 
CMakeLists.txt file seems to break the main test suite. When I run a full 
ctest, the main arrow-array-test target (which I believe is supposed to contain 
all the array tests) now fails.
   
   Here is the log from the full run:
   `99% tests passed, 1 tests failed out of 96
   ...
   The following tests FAILED:
   1 - arrow-array-test (Failed)`


-- 
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