Tracking tests disabled due to lack of gpu capable machines

[xmfcx]

Checklist

• I've read the contribution guidelines.
• I've searched other issues and no duplicate issues were found.
• I've agreed with the maintainers that I can plan this task.

Description

Story behind can be tracked from:

• build-and-test workflow is failing due to CUDA runtime version #7668 (comment)

Basically the tests disabled here:

• ✅ work on machines with Nvidia GPU
• ❌ fail on machines without Nvidia GPU

When we upgrade our testing infrastructure to have CUDA capable GPUs, we can re-enable these tests.

cc. @knzo25 @mitsudome-r

Sister issue:

• Tracking tests disabled because they were not tested by the CI before #7733

Purpose

To make CI pass on no-gpu machines. (Especially github hosted runners)

Possible approaches

• Commenting out the failing tests in the respective CMakeLists.txt file.
• Adding a reference to here

Definition of done

• build-and-test passes on the main branch.

Table of tracked tests

Link to commented section	Package Name	Related PR
autoware.universe/perception/lidar_centerpoint/CMakeLists.txt Lines 163 to 167 in e96334c # Temporary disabled, tracked by: # https://github.com/autowarefoundation/autoware.universe/issues/7724 # ament_auto_add_gtest(test_voxel_generator # test/test_voxel_generator.cpp # )	lidar_centerpoint	#7722
autoware.universe/perception/lidar_centerpoint/CMakeLists.txt Lines 169 to 207 in 891b231 # add_executable(test_preprocess_kernel # test/test_preprocess_kernel.cpp # lib/utils.cpp # ) # # target_include_directories(test_preprocess_kernel PUBLIC # ${test_preprocess_kernel_SOURCE_DIR} # ) # # target_link_libraries(test_preprocess_kernel # centerpoint_cuda_lib # gtest # gtest_main # ) # # ament_add_test(test_preprocess_kernel # GENERATE_RESULT_FOR_RETURN_CODE_ZERO # COMMAND "$<TARGET_FILE:test_preprocess_kernel>" # ) # # add_executable(test_postprocess_kernel # test/test_postprocess_kernel.cpp # lib/utils.cpp # ) # # target_include_directories(test_postprocess_kernel PUBLIC # ${test_postprocess_kernel_SOURCE_DIR} # ) # # target_link_libraries(test_postprocess_kernel # centerpoint_cuda_lib # gtest # gtest_main # ) # # ament_add_test(test_postprocess_kernel # GENERATE_RESULT_FOR_RETURN_CODE_ZERO # COMMAND "$<TARGET_FILE:test_postprocess_kernel>" # )	lidar_centerpoint	#7731

[xmfcx]

@mitsudome-r if somehow we gain access to gpu capable machines either by:

• adding more self hosted local machines
• or utilizing https://github.com/philips-labs/terraform-aws-github-runner

We can use this PR as reference:

• ci: run on gpu #7721

I will also create a documentation on how I set up the self hosted runners with custom init scripts.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity.

[knzo25]

@xmfcx
Is there any updates on this issue?
We would like to have the cuda tests enabled (https://github.com/autowarefoundation/autoware.universe/blob/main/perception/autoware_lidar_centerpoint/CMakeLists.txt)

[xmfcx]

@knzo25 please have a peek at:

• ci: use aws codebuild #8498

Through this new system, we have access to gpu1.small machines with 15 GB, 4vCPU and an unknown GPU, I didn't make any tests.

Full list: https://aws.amazon.com/codebuild/pricing/ (select us east n. virginia)

But this machine is pricier.

We only need GPU for tests, not for building with CUDA.

So one option would be to separate build and test in the workflow and test on this new machine.

But it requires someone to work on this task.