Skip to content

Updating & cleaning up GPU CI content #400

@jakirkham

Description

@jakirkham

Currently we have a number of references to gpuCI

##############################################
# Dask GPU build and test script for CI #
##############################################

CUDA_VER:
- "11.8.0"

dask-image/CONTRIBUTING.rst

Lines 194 to 212 in 458ac63

GPU continuous integration
^^^^^^^^^^^^^^^^^^^^^^^^^^^
We also have continuous integration to test GPU features!
This will run automatically, after a maintainer has approved it.
Maintainers approve the GPU CI to run by replying to the gpuCI bot on the
pull request, leaving a comment that says either *"ok to test"* or
*"add to allowlist"*.
The gpuCI bot `@GPUtester <https://github.com/GPUtester>`_
comment looks like this:
*Can one of the admins verify this patch?*
*Admins can comment ok to test to allow this one PR to run or add to allowlist to allow all future PRs from the same author to run.*
For more information about the GPU continuous integration provided by NVIIDIA,
`see the main Dask docs GPU CI section <https://docs.dask.org/en/stable/develop.html#gpu-ci>`_


Meanwhile we are working on replacing this with a new GPU CI procedure: rapidsai/dask-upstream-testing#39

Given this, we need to figure out what of the previous content is still needed, what needs updating, and what can be removed

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