Skip to content

Blackhole post-commit tests #1081

Blackhole post-commit tests

Blackhole post-commit tests #1081

Triggered via schedule October 9, 2024 02:26
Status Failure
Total duration 2h 11m 39s
Artifacts 11
build-docker-image  /  build-docker-image
49s
build-docker-image / build-docker-image
static-checks  /  check-spdx-licenses
55s
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
11s
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
2h 11m
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 49s
build-wheels / build-wheel
sd-unit-tests  /  blackhole BH
11m 55s
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
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.
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 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 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 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 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 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 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.
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.
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 ccl cpp 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.
umd-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/20241009030528_sys_logs.tar. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size
TTMetal_build_blackhole Expired
46.9 MB
eager-dist-ubuntu-20.04-blackhole Expired
371 MB
test_reports_10050533-663f-4287-a816-4807746c3fc1 Expired
36.1 KB
test_reports_51e7a296-356a-4469-9d90-a06ebc987564 Expired
8.2 KB
test_reports_6a4aeb14-5a43-42a5-b452-567797a1b918 Expired
7.17 KB
test_reports_6d92d7d2-85f6-40fc-a611-11b860c0d52c Expired
10.3 KB
test_reports_9ac8df8f-0126-4ad8-b5f0-38f3fec8960c Expired
3.79 KB
test_reports_a2d8422d-f0bc-4d8e-b133-44469b8663d6 Expired
5.67 KB
test_reports_b08be92c-25c4-4f09-9870-689b193d687a Expired
9.26 KB
test_reports_df5765cd-ec39-4e3e-8e56-f3ce763eb27c Expired
4.94 KB
test_reports_ed0c1f7a-4fec-4012-8ec4-80eecf393c6b Expired
872 Bytes