Blackhole post-commit tests #985
blackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
46s
static-checks
/
check-spdx-licenses
53s
static-checks
/
check-metal-kernel-count
8s
static-checks
/
check-black
41s
static-checks
/
check-doc
12s
static-checks
/
check-forbidden-imports
7s
static-checks
/
check-sweeps-workflow
6s
umd-unit-tests
/
blackhole BH
1m 7s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
10m 55s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
27 errors and 2 warnings
umd-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.
|
umd-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.
|
cpp-unit-tests / ttnn cpp 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.
|
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.
|
cpp-unit-tests / C++ 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 / C++ blackhole BH
The operation was canceled.
|
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.
|
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 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.
|
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.
|
fd-unit-tests / eager unit tests 6 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
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.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
TTMetal_build_blackhole
Expired
|
48.3 MB |
|
eager-dist-ubuntu-20.04-blackhole
Expired
|
370 MB |
|
test_reports_186ea42e-c25b-47a5-be0c-a8d13f4450cd
Expired
|
36.7 KB |
|
test_reports_1c0604c3-8d4b-4ffe-8d26-03d0fb56c147
Expired
|
5.72 KB |
|
test_reports_288d850f-5936-485d-8ff2-befef902e413
Expired
|
7.31 KB |
|
test_reports_3560e0a7-a247-4cc8-b40c-7ff78bee38c9
Expired
|
9.94 KB |
|
test_reports_5940e16a-e688-4236-a449-23b47d60566e
Expired
|
9.75 KB |
|
test_reports_7631011b-19e9-4ae7-9874-f0723a5b5135
Expired
|
1.8 KB |
|
test_reports_8ccf115a-7e2c-43ea-9d4b-d8553593074b
Expired
|
878 Bytes |
|
test_reports_c26eb984-8908-49a5-83d4-6d31cd9a3ad4
Expired
|
9.06 KB |
|