Skip to content

Blackhole post-commit tests #1078

Blackhole post-commit tests

Blackhole post-commit tests #1078

Triggered via schedule October 8, 2024 20:03
Status Failure
Total duration 1h 19m 35s
Artifacts 11
build-docker-image  /  build-docker-image
16s
build-docker-image / build-docker-image
static-checks  /  check-spdx-licenses
56s
static-checks / check-spdx-licenses
static-checks  /  check-metal-kernel-count
6s
static-checks / check-metal-kernel-count
static-checks  /  check-black
41s
static-checks / check-black
static-checks  /  check-doc
12s
static-checks / check-doc
static-checks  /  check-forbidden-imports
6s
static-checks / check-forbidden-imports
static-checks  /  check-sweeps-workflow
9s
static-checks / check-sweeps-workflow
umd-unit-tests  /  blackhole BH
1m 45s
umd-unit-tests / blackhole BH
build-artifact  /  ...  /  build-docker-image
build-artifact / build-docker-image / build-docker-image
Matrix: build-artifact / build-artifact
build-wheels  /  build-wheel
4m 33s
build-wheels / build-wheel
sd-unit-tests  /  blackhole BH
47m 44s
sd-unit-tests / blackhole BH
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Fit to window
Zoom out
Zoom in

Annotations

24 errors and 3 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 / 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 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 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 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 / 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 / ttnn cpp 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.
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.
sd-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.
cpp-unit-tests / ttnn ccl cpp unit tests blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh01 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/20241008205824_sys_logs.tar. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size
TTMetal_build_blackhole Expired
46.7 MB
eager-dist-ubuntu-20.04-blackhole Expired
371 MB
test_reports_1dcbf357-febc-4bb1-b90e-c09b5fa623bb Expired
3.79 KB
test_reports_4492e2ef-c9f2-4df8-9fda-38287d136844 Expired
36 KB
test_reports_4c7a4387-1367-442c-9f6a-737846c1c9bc Expired
876 Bytes
test_reports_5384ff2f-f8f9-4d8b-a525-ae966f023c74 Expired
5.68 KB
test_reports_8c637b81-e211-4a91-ace7-1e43e5498fdf Expired
9.27 KB
test_reports_9f3ea08a-6d26-420f-93a3-fe6bee3a8da4 Expired
10.4 KB
test_reports_c675a002-339d-40fd-bb47-2a645a66fced Expired
4.94 KB
test_reports_e1e8981c-5fc2-4588-822f-672776ced668 Expired
7.18 KB
test_reports_fe26097c-f0d4-4983-a8e6-39b503c7e6ea Expired
8.23 KB