Blackhole post-commit tests #997
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
39s
static-checks
/
check-doc
12s
static-checks
/
check-forbidden-imports
8s
static-checks
/
check-sweeps-workflow
9s
umd-unit-tests
/
blackhole BH
1m 8s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
42m 48s
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 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.
|
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.
|
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.
|
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 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 / 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 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 / 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.
|
sd-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.
|
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
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
TTMetal_build_blackhole
Expired
|
48.3 MB |
|
eager-dist-ubuntu-20.04-blackhole
Expired
|
371 MB |
|
test_reports_0120cc4d-5496-4b16-a2d9-700e7ca0ec36
Expired
|
4.94 KB |
|
test_reports_5153eef7-a78c-465d-92cd-ea46344eb385
Expired
|
8.3 KB |
|
test_reports_79cde4ac-9e1f-48d6-9896-b50a25d4d908
Expired
|
1.17 KB |
|
test_reports_9097f221-d9c2-4157-b301-7ba8e6d0a140
Expired
|
7.19 KB |
|
test_reports_9974e477-8867-414b-9469-f28ec91676b7
Expired
|
10.5 KB |
|
test_reports_b4387b77-e1aa-4e0f-9c18-15c2e99883a0
Expired
|
35.2 KB |
|
test_reports_b906f135-02d2-4f9d-816a-0c40bd3457ff
Expired
|
3.84 KB |
|
test_reports_cb5127b9-91e4-469d-90b6-2bc9b4d2efc7
Expired
|
878 Bytes |
|