Skip to content

retry 5 times

retry 5 times #2165

Triggered via push July 23, 2024 20:40
Status Cancelled
Total duration 26m 38s
Artifacts

test.yml

on: push
Check PR Event
0s
Check PR Event
Build  /  Check GH Event
0s
Build / Check GH Event
Validate Features
18s
Validate Features
Matrix: Build / RAPIDS / build
Determine features matrix
7s
Determine features matrix
Determine image matrix
6s
Determine image matrix
Matrix: Feature integration / test
Matrix: run-feature-scenario-tests
Matrix: run-generated-feature-tests
Matrix: build-and-test-linux-images
Matrix: build-and-test-windows-images
Fit to window
Zoom out
Zoom in

Annotations

135 errors and 16 warnings
Test llvm scenarios / amd64
Process completed with exit code 1.
Build / RAPIDS / build (amd64, 12.5, pip)
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
Build / RAPIDS / build (amd64, 12.5, pip)
The self-hosted runner: linux-amd64-cpu32-76j4m-runner-sfndd 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.
Build / RAPIDS / build (amd64, 12.0, conda)
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
Build / RAPIDS / build (amd64, 12.0, conda)
The self-hosted runner: linux-amd64-cpu32-76j4m-runner-blw6z 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.
Build / RAPIDS / build (amd64, 12.5, conda)
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
Build / RAPIDS / build (amd64, 12.5, conda)
The self-hosted runner: linux-amd64-cpu32-76j4m-runner-fldjn 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.
Build / RAPIDS / build (amd64, 12.0, pip)
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
Build / RAPIDS / build (amd64, 12.0, pip)
The self-hosted runner: linux-amd64-cpu32-76j4m-runner-2wrm2 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.
Feature integration / amd64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
Feature integration / amd64
The self-hosted runner: linux-amd64-cpu4-btl7p-runner-mv857 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.
Feature integration / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
Feature integration / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-5g6pv 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.
llvm10-cuda12.5-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm10-cuda12.5-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-zhnsf 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.
llvm12-cuda12.0-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm12-cuda12.0-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-qdsvw 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.
llvm14-cuda12.5-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm14-cuda12.5-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-wsttb 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.
llvm11-cuda12.5-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm11-cuda12.5-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-tqcxc 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.
llvm9-cuda12.5-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm9-cuda12.5-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-4z6sn 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.
llvm11-cuda12.0-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm11-cuda12.0-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-xcrzp 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.
llvm13-cuda12.5-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm13-cuda12.5-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-z5zrd 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.
llvm19-cuda12.5-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm19-cuda12.5-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-7q968 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.
gcc9-cuda12.5-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc9-cuda12.5-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-z4lm4 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.
llvm10-cuda12.0-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm10-cuda12.0-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-gn4v8 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.
llvm16-cuda12.0-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm16-cuda12.0-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-rgjff 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.
llvm18-cuda12.5-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm18-cuda12.5-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-zf4sz 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.
llvm16-cuda12.5-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm16-cuda12.5-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-84vw6 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.
gcc7-cuda12.0-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc7-cuda12.0-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-dfhf5 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.
oneapi2023.2.0-cuda12.5-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
oneapi2023.2.0-cuda12.5-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-cv88x 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.
cuda12.5-ucx1.17.0-openmpi-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.5-ucx1.17.0-openmpi-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-vkmzc 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.
gcc9-cuda12.0-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc9-cuda12.0-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-2hlfn 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.
llvm17-cuda12.0-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm17-cuda12.0-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-fr8gl 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.
cuda11.8-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda11.8-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-2dxn9 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.
cuda12.0-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.0-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-cnq79 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.
cuda12.5-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.5-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-5ngfg 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.
llvm15-cuda12.0-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm15-cuda12.0-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-k277z 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.
nvhpc24.5-ubuntu:22.04 / amd64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
nvhpc24.5-ubuntu:22.04 / amd64
The self-hosted runner: linux-amd64-cpu4-btl7p-runner-47js4 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.
cuda11.8-ucx1.17.0-openmpi-ubuntu:22.04 / amd64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda11.8-ucx1.17.0-openmpi-ubuntu:22.04 / amd64
The self-hosted runner: linux-amd64-cpu4-btl7p-runner-vd5tf 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.
gcc11-cuda12.0-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc11-cuda12.0-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-c879f 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.
gcc12-cuda12.0-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc12-cuda12.0-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-cxw86 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.
gcc12-cuda12.5-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc12-cuda12.5-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-zqxb8 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.
nvhpc24.3-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc11-cuda11.8-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
nvhpc24.3-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-pnjxz 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.
gcc11-cuda11.8-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-v998z 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.
cuda12.0-ucx1.17.0-openmpi-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.0-ucx1.17.0-openmpi-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-kml4s 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.
gcc13-cuda12.5-ubuntu:23.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc13-cuda12.5-ubuntu:23.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-x78ms 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.
gcc13-cuda12.0-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc13-cuda12.0-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-jhwm9 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.
nvhpc24.5-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
nvhpc24.5-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-xzzdx 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.
gcc11-cuda12.5-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc11-cuda12.5-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-m94kz 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.
cuda11.1-cl14.28-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda11.1-cl14.28-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-4fb6d 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.
cuda12.0-cl14.29-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.0-cl14.29-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-x2kpp 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.
cuda12.5-cl14.28-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.5-cl14.28-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-h47pb 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.
cuda11.1-cl14.15-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda11.1-cl14.15-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-2ffkw 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.
cuda12.5-cl14.15-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.5-cl14.15-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-trkz2 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.
cuda12.5-cl14.38-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.5-cl14.38-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-n7q7q 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.
cuda11.1-cl14.29-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda11.1-cl14.29-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-ggfr4 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.
cuda11.1-cl14.27-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda11.1-cl14.27-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-fgvx9 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.
cuda11.1-cl14.14-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda11.1-cl14.14-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-4dntz 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.
cuda12.5-cl14.29-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.5-cl14.29-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-qfzxk 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.
cuda11.1-cl14.16-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda11.1-cl14.16-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-8xmhz 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.
cuda12.0-cl14.36-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.0-cl14.36-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-wbjrg 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.
cuda12.0-ucx1.17.0-openmpi-ubuntu:22.04 / amd64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.0-ucx1.17.0-openmpi-ubuntu:22.04 / amd64
The self-hosted runner: linux-amd64-cpu4-btl7p-runner-sppcb 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.
cuda12.5-ucx1.17.0-openmpi-ubuntu:22.04 / amd64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.5-ucx1.17.0-openmpi-ubuntu:22.04 / amd64
The self-hosted runner: linux-amd64-cpu4-btl7p-runner-249cq 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.
nvhpc24.3-ubuntu:22.04 / amd64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
nvhpc24.3-ubuntu:22.04 / amd64
The self-hosted runner: linux-amd64-cpu4-btl7p-runner-wp5mx 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.
gcc8-cuda12.0-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc8-cuda12.0-ubuntu:20.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-gtbtz 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.
llvm17-cuda12.5-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm17-cuda12.5-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-4rx72 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.
llvm19-cuda12.0-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm19-cuda12.0-ubuntu:22.04 / arm64
The self-hosted runner: linux-arm64-cpu4-l9kfv-runner-rlpdx 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.
cuda12.5-cl14.27-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.5-cl14.27-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-46hrg 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.
Test llvm scenarios / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
Test utils scenarios / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.5-cl14.16-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.5-cl14.37-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.5-cl14.39-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda12.5-cl14.14-windows / 2022
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm14-cuda12.0-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm13-cuda12.0-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc10-cuda12.5-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm15-cuda12.5-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm9-cuda12.0-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
llvm18-cuda12.0-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc7-cuda12.5-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc10-cuda12.0-ubuntu:20.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
gcc13-cuda12.5-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
cuda11.8-ucx1.17.0-openmpi-ubuntu:22.04 / arm64
Canceling since a higher priority waiting request for 'test-from-pull-request/369' exists
Test llvm scenarios / arm64
Runner linux-arm64-cpu4-l9kfv-runner-5884x did not respond to a cancelation request with 00:05:00.
Test utils scenarios / arm64
Runner linux-arm64-cpu4-l9kfv-runner-b8g2h did not respond to a cancelation request with 00:05:00.
cuda12.5-cl14.16-windows / 2022
Runner windows-amd64-cpu4-x5wm8-runner-cgq6q did not respond to a cancelation request with 00:05:00.
cuda12.5-cl14.37-windows / 2022
Runner windows-amd64-cpu4-x5wm8-runner-nv4cc did not respond to a cancelation request with 00:05:00.
cuda12.5-cl14.39-windows / 2022
Runner windows-amd64-cpu4-x5wm8-runner-hsqdp did not respond to a cancelation request with 00:05:00.
cuda12.5-cl14.14-windows / 2022
Runner windows-amd64-cpu4-x5wm8-runner-zm2kl did not respond to a cancelation request with 00:05:00.
llvm13-cuda12.0-ubuntu:20.04 / arm64
Runner linux-arm64-cpu4-l9kfv-runner-jtrsf did not respond to a cancelation request with 00:05:00.
llvm14-cuda12.0-ubuntu:20.04 / arm64
Runner linux-arm64-cpu4-l9kfv-runner-b7v8r did not respond to a cancelation request with 00:05:00.
gcc10-cuda12.5-ubuntu:20.04 / arm64
Runner linux-arm64-cpu4-l9kfv-runner-gjlmx did not respond to a cancelation request with 00:05:00.
llvm15-cuda12.5-ubuntu:22.04 / arm64
Runner linux-arm64-cpu4-l9kfv-runner-z6rbj did not respond to a cancelation request with 00:05:00.
llvm9-cuda12.0-ubuntu:20.04 / arm64
Runner linux-arm64-cpu4-l9kfv-runner-xhqjn did not respond to a cancelation request with 00:05:00.
llvm18-cuda12.0-ubuntu:22.04 / arm64
Runner linux-arm64-cpu4-l9kfv-runner-wsfjt did not respond to a cancelation request with 00:05:00.
gcc7-cuda12.5-ubuntu:20.04 / arm64
Runner linux-arm64-cpu4-l9kfv-runner-xd6qz did not respond to a cancelation request with 00:05:00.
gcc10-cuda12.0-ubuntu:20.04 / arm64
Runner linux-arm64-cpu4-l9kfv-runner-bwdhl did not respond to a cancelation request with 00:05:00.
gcc13-cuda12.5-ubuntu:22.04 / arm64
Runner linux-arm64-cpu4-l9kfv-runner-pp5cd did not respond to a cancelation request with 00:05:00.
cuda11.8-ucx1.17.0-openmpi-ubuntu:22.04 / arm64
Runner linux-arm64-cpu4-l9kfv-runner-qgk59 did not respond to a cancelation request with 00:05:00.