Blackhole post-commit tests #1084
ttmchioublackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
18s
static-checks
/
check-spdx-licenses
50s
static-checks
/
check-metal-kernel-count
5s
static-checks
/
check-black
40s
static-checks
/
check-doc
11s
static-checks
/
check-forbidden-imports
9s
static-checks
/
check-sweeps-workflow
11s
umd-unit-tests
/
blackhole BH
2h 13m
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
12m 14s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
25 errors and 3 warnings
|
cpp-unit-tests / ttnn ccl cpp 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.
|
|
cpp-unit-tests / ttnn ccl cpp unit tests blackhole BH
The operation was canceled.
|
|
cpp-unit-tests / ttnn cpp 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 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.
|
|
fd-unit-tests / eager trace 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.
|
|
fd-unit-tests / eager trace tests blackhole BH
The operation was canceled.
|
|
fd-unit-tests / eager unit tests 2 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.
|
|
fd-unit-tests / eager unit tests 2 blackhole BH
The operation was canceled.
|
|
fd-unit-tests / eager unit tests 3 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.
|
|
fd-unit-tests / eager unit tests 3 blackhole BH
The operation was canceled.
|
|
fd-unit-tests / eager unit tests 4 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.
|
|
fd-unit-tests / eager unit tests 4 blackhole BH
The operation was canceled.
|
|
fd-unit-tests / eager unit tests 5 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.
|
|
fd-unit-tests / eager unit tests 5 blackhole BH
The operation was canceled.
|
|
fd-unit-tests / eager unit tests 6 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.
|
|
fd-unit-tests / eager unit tests 6 blackhole BH
The operation was canceled.
|
|
fd-unit-tests / eager unit tests 1 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.
|
|
fd-unit-tests / eager unit tests 1 blackhole BH
The operation was canceled.
|
|
fd-unit-tests / eager unit tests 7 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.
|
|
fd-unit-tests / eager unit tests 7 blackhole BH
The operation was canceled.
|
|
cpp-unit-tests / C++ 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 / sweep 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.
|
|
fd-unit-tests / sweep blackhole BH
The operation was canceled.
|
|
umd-unit-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.
|
|
build-wheels / build-wheel
Cache paths are empty. Please check the previous logs and make sure that the python version is specified
|
|
build-wheels / build-wheel
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
fd-unit-tests / eager unit tests 6 blackhole BH
No files were found with the provided path: ~/run-log/20241009085341_sys_logs.tar. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
TTMetal_build_blackhole
Expired
|
47 MB |
|
|
eager-dist-ubuntu-20.04-blackhole
Expired
|
371 MB |
|
|
test_reports_0323121a-572e-49a8-b22b-f2a1ed43640f
Expired
|
35.7 KB |
|
|
test_reports_191badf5-3e6f-4e3a-9a0f-e760e6516bec
Expired
|
7.12 KB |
|
|
test_reports_39f34294-9efb-4217-8efe-59dc5cf855c2
Expired
|
3.75 KB |
|
|
test_reports_550f82ab-2a01-4e41-aa34-ada67a88689d
Expired
|
8.28 KB |
|
|
test_reports_634cac25-d402-4011-ba38-dbeea15ce6a2
Expired
|
10.3 KB |
|
|
test_reports_7a161062-8998-4bf6-a512-beaea868935e
Expired
|
4.92 KB |
|
|
test_reports_8564e918-9900-434b-830b-746ba00e9ef7
Expired
|
876 Bytes |
|
|
test_reports_99e6a426-890b-4e03-b7d0-131a4ca9a8b8
Expired
|
5.68 KB |
|
|
test_reports_b1073039-580c-4b9a-9093-ef7832038a45
Expired
|
9.2 KB |
|