Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Cuda test workflow for push action in sycl_develop #216

Open
wants to merge 1 commit into
base: sycl-develop
Choose a base branch
from

Conversation

aacostadiaz
Copy link
Collaborator

This PR introduces a cuda test workflow triggered on push actions in the sycl_develop branch. The workflow will build the entire library which may take a considerable amount of time

@aacostadiaz aacostadiaz requested a review from carlewis February 14, 2025 16:35
@carlewis
Copy link
Member

Unless I'm missing some detail, if we are not going to run anything in the device, but only build the code we can take a different approach.

We can use runs-on: ubuntu-22.04 or runs-on: ubuntu-latest, and also use a public docker image with CUDA installed. There are a few different tags available here:

https://hub.docker.com/r/nvidia/cuda/tags

Something like: image: nvidia/gpu:12.8.0-base-ubuntu22.04

This way the GPU runner won't be monopolized by this workflow.

@aacostadiaz
Copy link
Collaborator Author

Unless I'm missing some detail, if we are not going to run anything in the device, but only build the code we can take a different approach.

We can use runs-on: ubuntu-22.04 or runs-on: ubuntu-latest, and also use a public docker image with CUDA installed. There are a few different tags available here:

https://hub.docker.com/r/nvidia/cuda/tags

Something like: image: nvidia/gpu:12.8.0-base-ubuntu22.04

This way the GPU runner won't be monopolized by this workflow.

it is running the unit tests on device too. cmake --build . --target test_unit -j 48 will do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants