Skip to content
CI

Lazy load code modules (#269) #349

Sign in to view logs

Lazy load code modules (#269)

Lazy load code modules (#269) #349

Re-run triggered December 11, 2024 17:03
@leofangleofang
64cbc4c
main
Status Failure
Total duration 55m 1s
Artifacts 30

ci-gh.yml

on: push
Matrix: CI
Fit to window
Zoom out
Zoom in

Annotations

5 errors
CI (linux-x64, gpu, release, false, 3.11, 12.6.2) / Test (CUDA 12.6.2)
The self-hosted runner: linux-amd64-gpu-v100-latest-1-xbjv8-runner-89nqw 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.
CI (linux-x64, gpu, release, false, 3.10, 12.6.2) / Test (CUDA 12.6.2)
The self-hosted runner: linux-amd64-gpu-v100-latest-1-xbjv8-runner-8rsvf 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.
CI (linux-x64, gpu, release, false, 3.12, 12.6.2) / Test (CUDA 12.6.2)
The self-hosted runner: linux-amd64-gpu-v100-latest-1-xbjv8-runner-g75qg 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.
CI (linux-x64, gpu, release, false, 3.13, 12.6.2) / Test (CUDA 12.6.2)
The self-hosted runner: linux-amd64-gpu-v100-latest-1-xbjv8-runner-2kh9d 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.
CI (linux-x64, gpu, release, false, 3.9, 12.6.2) / Test (CUDA 12.6.2)
The self-hosted runner: linux-amd64-gpu-v100-latest-1-xbjv8-runner-6t9r9 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.

Artifacts

Produced during runtime
Name Size
cuda-bindings-python313-cuda12.6.2-win-x64-ci-64cbc4c2a600cca5c9eba166fb21091a4c1f0d46
9.81 MB
cuda-core-python313-win-x64-ci-64cbc4c2a600cca5c9eba166fb21091a4c1f0d46
406 KB