Skip to content

allow to continue run tests even if ruche CI fails #391

allow to continue run tests even if ruche CI fails

allow to continue run tests even if ruche CI fails #391

Triggered via pull request November 4, 2024 11:07
Status Failure
Total duration 20m 34s
Artifacts 8

build_test.yaml

on: pull_request
check_docker_files  /  check_docker_files
4s
check_docker_files / check_docker_files
Matrix: build_base / build_base
Waiting for pending jobs
Matrix: build
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 1 warning
test (false, cuda, nvcc, self-hosted, cuda, true)
Process completed with exit code 255.
test (false, threads, gcc, ubuntu-latest)
The job was canceled because "false_cuda_nvcc_self-host" failed.
test (false, threads, gcc, ubuntu-latest)
The operation was canceled.
test (false, openmp, gcc, ubuntu-latest)
The job was canceled because "false_cuda_nvcc_self-host" failed.
test (false, openmp, gcc, ubuntu-latest)
The operation was canceled.
test (false, serial, gcc, ubuntu-latest)
The job was canceled because "false_cuda_nvcc_self-host" failed.
test (false, serial, gcc, ubuntu-latest)
The operation was canceled.
test (false, cuda, nvcc, self-hosted, cuda, true)
You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 15 MB

Artifacts

Produced during runtime
Name Size
tests_clang-tidy
49.3 MB
tests_cuda
20.6 MB
tests_hip
17.3 MB
tests_openmp
83.5 MB
tests_rocm
18.3 MB
tests_serial
13 MB
tests_sycl
29.9 MB
tests_threads
12.6 MB