Merge branch 'branch-24.08' into testing-on-demand-jobs #5591
pr.yaml
on: push
Matrix: devcontainer / build
wheel-build-cugraph-equivariant
/
compute-matrix
2s
Matrix: wheel-build-cugraph-equivariant / build
Matrix: conda-cpp-build / build
Matrix: wheel-build-pylibcugraph / build
wheel-tests-cugraph-equivariant
/
compute-matrix
2s
Matrix: wheel-tests-cugraph-equivariant / test
Matrix: conda-cpp-tests / tests
Matrix: conda-python-build / build
Matrix: wheel-tests-pylibcugraph / test
conda-notebook-tests
/
build
19m 45s
docs-build
/
build
15m 35s
Matrix: conda-python-tests / tests
Matrix: wheel-build-cugraph / build
Matrix: wheel-build-nx-cugraph / build
Matrix: wheel-tests-cugraph / test
Matrix: wheel-tests-nx-cugraph / test
Matrix: wheel-build-cugraph-dgl / build
Waiting for pending jobs
Matrix: wheel-build-cugraph-pyg / build
Waiting for pending jobs
Matrix: wheel-tests-cugraph-dgl / test
Waiting for pending jobs
Matrix: wheel-tests-cugraph-pyg / test
Waiting for pending jobs
pr-builder
/
run
Annotations
3 errors
wheel-tests-cugraph / 12.5.1, 3.9, amd64, ubuntu22.04, v100
The self-hosted runner: linux-amd64-gpu-v100-latest-1-56xmt-runner-tzlfs lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
conda-python-tests / tests (amd64, 3.9, 11.8.0, rockylinux8, v100, earliest)
The self-hosted runner: linux-amd64-gpu-v100-earliest-1-bbxjq-runner-sx8ln lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
conda-python-tests / tests (amd64, 3.11, 12.5.1, ubuntu22.04, v100, latest)
The self-hosted runner: linux-amd64-gpu-v100-latest-1-56xmt-runner-r65dn lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|