Open xmfcx opened 3 months ago
@mitsudome-r if somehow we gain access to gpu capable machines either by:
We can use this PR as reference:
I will also create a documentation on how I set up the self hosted runners with custom init scripts.
This pull request has been automatically marked as stale because it has not had recent activity.
@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)
@knzo25 please have a peek at:
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.
Checklist
Description
Story behind can be tracked from:
Basically the tests disabled here:
When we upgrade our testing infrastructure to have CUDA capable GPUs, we can re-enable these tests.
cc. @knzo25 @mitsudome-r
Sister issue:
Purpose
To make CI pass on no-gpu machines. (Especially github hosted runners)
Possible approaches
Definition of done
build-and-test
passes on the main branch.Table of tracked tests