Blackhole post-commit tests #1250
ttmchioublackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
13s
static-checks
/
check-spdx-licenses
49s
static-checks
/
check-metal-kernel-count
5s
static-checks
/
check-black
29s
static-checks
/
check-doc
11s
static-checks
/
check-forbidden-imports
6s
static-checks
/
check-sweeps-workflow
7s
static-checks
/
clang-tidy
0s
umd-unit-tests
/
blackhole BH
43m 5s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
14m 4s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
6 errors and 3 warnings
|
sd-unit-tests / blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
sd-unit-tests / blackhole BH
The operation was canceled.
|
|
umd-unit-tests / blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh04 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.
|
|
cpp-unit-tests / ttnn cpp tests blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh03 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.
|
|
fd-unit-tests / eager unit tests 2 blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh04 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.
|
|
fd-unit-tests / eager unit tests 1 blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh04 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-wheels / build-wheel
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
build-wheels / build-wheel
Cache paths are empty. Please check the previous logs and make sure that the python version is specified
|
|
fd-unit-tests / eager unit tests 6 blackhole BH
No files were found with the provided path: ~/run-log/20241021193244_sys_logs.tar. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
TTMetal_build_blackhole
|
47.1 MB |
|
|
eager-dist-ubuntu-20.04-blackhole
|
372 MB |
|
|
test_reports_0191fa2e-3187-4574-a586-d0e84d392031
|
9.16 KB |
|
|
test_reports_21eefaee-41ff-41fd-82e1-1026365e076d
|
4.87 KB |
|
|
test_reports_25541174-a550-457f-b8fc-bec64225638a
|
870 Bytes |
|
|
test_reports_318c2788-50c0-44de-8cdc-af5c797a90f5
|
9.55 KB |
|
|
test_reports_59b1e2f1-55e9-4e49-9464-68005a8b104c
|
8.01 KB |
|
|
test_reports_6abca284-6f2e-4ae9-854a-9262bd134e1b
|
9.32 KB |
|
|
test_reports_dc3ad012-71e0-4cdc-98d5-072ef853e7e2
|
36.1 KB |
|