Blackhole post-commit tests #988
blackhole-post-commit.yaml
on: workflow_dispatch
build-docker-image
/
build-docker-image
40s
static-checks
/
check-spdx-licenses
48s
static-checks
/
check-metal-kernel-count
7s
static-checks
/
check-black
38s
static-checks
/
check-doc
12s
static-checks
/
check-forbidden-imports
5s
static-checks
/
check-sweeps-workflow
7s
umd-unit-tests
/
blackhole BH
1m 38s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
11m 26s
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.
|
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 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 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 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 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 / 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 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.
|
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.
|
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.4 MB |
|
eager-dist-ubuntu-20.04-blackhole
Expired
|
371 MB |
|
test_reports_05cc31cf-d94e-45da-92aa-b71632210b18
Expired
|
9.28 KB |
|
test_reports_2b702b59-4277-4379-873e-09347569ceee
Expired
|
7.18 KB |
|
test_reports_2dd553fc-c963-41f5-8b53-e81e38d61252
Expired
|
4.94 KB |
|
test_reports_5f8ad0e1-c794-4552-be6b-db2c96484ab0
Expired
|
10.5 KB |
|
test_reports_acad27dc-b789-44cd-9d7e-bc9feab3518b
Expired
|
873 Bytes |
|
test_reports_b320c83f-616e-4341-8732-95e8e8e759ca
Expired
|
8.25 KB |
|
test_reports_cce55fc0-5225-4cd1-bf98-5da26ba4a488
Expired
|
36.8 KB |
|
test_reports_dbc71bf9-1d0f-4988-9c56-3122037d5016
Expired
|
1.17 KB |
|
test_reports_f85aad2c-3dc8-42ac-9339-81996a1a95c0
Expired
|
3.87 KB |
|