Skip to content

Strategy for running CI-tests against GPU machines #227

Closed
@nils-braun

Description

@nils-braun

With the recent integration of dask-cudf into dask-sql, it would be wise to start testing against GPU libraries and machines in the automated build triggered by GitHub actions.

@ayushdg mentioned on #220, that:

GpuCI is one option that could be used to test integration with rapids libraries. It's what the dask repository uses as well (dask/community#138).
I don't think it uses GitHub actions specifically but is enabled via a webhook to GitHub.

I would be very much interested, if this is also an option for dask-contrib packages (and if this would be supported by RAPIDS) and what the current experience with the setup at the dask main repository is. Maybe, @quasiben, @jrbourbeau, can you shortly summarize the current setup in the dask main repository and how the experiences are? Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions