Skip to content

build

build #472

Manually triggered July 12, 2023 06:39
Status Failure
Total duration 3h 49m 15s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

build.yaml

on: workflow_dispatch
cpp-build  /  compute-matrix
1s
cpp-build / compute-matrix
wheel-build-pylibcugraph  /  wheel epoch timestamper
2s
wheel-build-pylibcugraph / wheel epoch timestamper
wheel-build-pylibcugraph  /  compute-matrix
2s
wheel-build-pylibcugraph / compute-matrix
Matrix: cpp-build / build
Matrix: wheel-build-pylibcugraph / wheel-build
python-build  /  compute-matrix
python-build / compute-matrix
wheel-publish-pylibcugraph  /  wheels publish
10m 38s
wheel-publish-pylibcugraph / wheels publish
Matrix: python-build / build
Waiting for pending jobs
wheel-build-cugraph  /  wheel epoch timestamper
2s
wheel-build-cugraph / wheel epoch timestamper
wheel-build-cugraph  /  compute-matrix
1s
wheel-build-cugraph / compute-matrix
upload-conda  /  upload
upload-conda / upload
docs-build  /  build
docs-build / build
Matrix: wheel-build-cugraph / wheel-build
wheel-publish-cugraph  /  wheels publish
11m 41s
wheel-publish-cugraph / wheels publish
Fit to window
Zoom out
Zoom in

Annotations

4 errors
cpp-build / build (11.8.0, ubuntu22.04, amd64, 3.10)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
cpp-build / build (11.8.0, ubuntu22.04, amd64, 3.10)
Process completed with exit code 130.
cpp-build / build (11.8.0, ubuntu22.04, amd64, 3.10)
The operation was canceled.
cpp-build / build (11.8.0, ubuntu22.04, arm64, 3.10)
The self-hosted runner: rapidsai-linux-arm64-cpu8-q5bj5-runner-c5rx8 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.