Skip to content

Blackhole post-commit tests #1068

Blackhole post-commit tests

Blackhole post-commit tests #1068

Triggered via schedule October 8, 2024 06:05
Status Failure
Total duration 2h 22m 30s
Artifacts 10
build-docker-image  /  build-docker-image
47s
build-docker-image / build-docker-image
static-checks  /  check-spdx-licenses
47s
static-checks / check-spdx-licenses
static-checks  /  check-metal-kernel-count
6s
static-checks / check-metal-kernel-count
static-checks  /  check-black
39s
static-checks / check-black
static-checks  /  check-doc
10s
static-checks / check-doc
static-checks  /  check-forbidden-imports
8s
static-checks / check-forbidden-imports
static-checks  /  check-sweeps-workflow
11s
static-checks / check-sweeps-workflow
umd-unit-tests  /  blackhole BH
1m 38s
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 56s
build-wheels / build-wheel
sd-unit-tests  /  blackhole BH
2h 11m
sd-unit-tests / blackhole BH
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Fit to window
Zoom out
Zoom in

Annotations

21 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 / 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.
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 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 3 blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh02 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 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 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.
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.
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.
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/20241008064024_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_219370a0-3079-4453-b912-c6d0e87fe20a Expired
34.8 KB
test_reports_2ab8fa26-c3cf-4770-a393-92895220de3c Expired
4.94 KB
test_reports_9bc92fe4-4662-4cca-aa27-92762a163c99 Expired
10.2 KB
test_reports_a4492515-f2ff-4750-8166-ee8ca1febff3 Expired
5.67 KB
test_reports_d2028ace-48af-489d-9f16-4f8e3d4b48ea Expired
7.14 KB
test_reports_d91bf7ed-904d-4b3d-b24d-3cc0b172018d Expired
8.18 KB
test_reports_e4c7ed19-8ae3-4790-9c08-8310995fb8b8 Expired
3.79 KB
test_reports_eb828fa0-3b03-44b4-aede-523e57ed34ae Expired
871 Bytes