Closed Rhett-Ying closed 2 months ago
To trigger regression tests:
@dgl-bot run [instance-type] [which tests] [compare-with-branch]
;
For example: @dgl-bot run g4dn.4xlarge all dmlc/master
or @dgl-bot run c5.9xlarge kernel,api dmlc/master
@TristonC
We're updating the minimum pytorch version from 2.0.0
to 2.1.0
and CI is blocked by cugraph docker image: rapidsai/cugraph_stable_torch-cuda:11.8-base-ubuntu20.04-py3.10-pytorch2.0.0-rapids23.04
.
On the web page: https://hub.docker.com/r/rapidsai/cugraph_stable_torch-cuda, I cannot find any newer ones.
So do you have ideas about how to handle this?
@dgl-bot
@TristonC
We're updating the minimum pytorch version from
2.0.0
to2.1.0
and CI is blocked by cugraph docker image:rapidsai/cugraph_stable_torch-cuda:11.8-base-ubuntu20.04-py3.10-pytorch2.0.0-rapids23.04
.On the web page: https://hub.docker.com/r/rapidsai/cugraph_stable_torch-cuda, I cannot find any newer ones.
So do you have ideas about how to handle this?
@chang-l Hi, do you have any suggestion on this? Should we bypass the test on cugraph or upgrade docker image?
@Rhett-Ying, can you please try switch to NVIDIA's public NGC DGL container for your CI/CD?(https://catalog.ngc.nvidia.com/orgs/nvidia/containers/dgl) docker pull nvcr.io/nvidia/dgl:24.04-py3
It includes latest PyTorch and latest RAPIDS (e.g., cugraph/wholegraph) for graph analysis.
@Rhett-Ying We can pause (bypass) the cugraph test for now. cugraph is in the process of refactoring. We can add the test back once its ready. Or as @chang-l suggested to use NVIDIA DGL container.
@Rhett-Ying We can pause (bypass) the cugraph test for now. cugraph is in the process of refactoring. We can add the test back once its ready. Or as @chang-l suggested to use NVIDIA DGL container.
Sure. Let's pause the cugraph test for now.
And is there any ticket link to track the status of cugraph refactoring? we could link it here.
Description
Checklist
Please feel free to remove inapplicable items for your PR.
Changes