Skip to content

Blackhole post-commit tests #1069

Blackhole post-commit tests

Blackhole post-commit tests #1069

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

Annotations

20 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.
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 / 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.
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.
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 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 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 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 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 / 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-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 2 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/20241008083853_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_1ad1f66e-cdce-4b20-b201-0486d80286d0 Expired
8.18 KB
test_reports_2eacd2f6-1b00-43b9-a43c-70fbd081030f Expired
10.2 KB
test_reports_33e6e8ef-e310-4ac5-a7ef-5fdd06d8a119 Expired
880 Bytes
test_reports_427469a8-ca9b-48ac-a57f-64d9f856f05e Expired
7.07 KB
test_reports_91135270-2361-4d7a-9269-604407326976 Expired
9.25 KB
test_reports_d269bf8d-29c5-4508-96ef-bde725cd6eb4 Expired
36.1 KB
test_reports_f2205477-b654-443a-b0db-5d3c39219458 Expired
5.69 KB
test_reports_f5fb9f18-7e14-4cc3-8ab4-0eb6c7d61868 Expired
3.79 KB