-
-
Notifications
You must be signed in to change notification settings - Fork 54
Closed
Description
Currently we have a number of references to gpuCI
dask-image/continuous_integration/gpuci/build.sh
Lines 1 to 3 in 458ac63
| ############################################## | |
| # Dask GPU build and test script for CI # | |
| ############################################## |
dask-image/continuous_integration/gpuci/axis.yaml
Lines 6 to 7 in 458ac63
| CUDA_VER: | |
| - "11.8.0" |
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels