Blackhole post-commit tests #1034
blackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
42s
static-checks
/
check-spdx-licenses
53s
static-checks
/
check-metal-kernel-count
7s
static-checks
/
check-black
38s
static-checks
/
check-doc
12s
static-checks
/
check-forbidden-imports
7s
static-checks
/
check-sweeps-workflow
7s
umd-unit-tests
/
blackhole BH
1m 39s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
11m 17s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
25 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.
|
cpp-unit-tests / ttnn ccl cpp 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 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.
|
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.
|
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 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 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 5 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 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 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.
|
fd-unit-tests / sweep blackhole BH
The operation was canceled.
|
fd-unit-tests / eager unit tests 6 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.
|
fd-unit-tests / eager unit tests 7 blackhole BH
No files were found with the provided path: ~/run-log/20241005163235_sys_logs.tar. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
TTMetal_build_blackhole
Expired
|
48.6 MB |
|
eager-dist-ubuntu-20.04-blackhole
Expired
|
371 MB |
|
test_reports_1b4987bd-735d-4294-9aa6-05f5ae79642f
Expired
|
878 Bytes |
|
test_reports_3d4f525b-751c-43c7-b57a-296ca932f775
Expired
|
9.27 KB |
|
test_reports_49b7182d-f5a8-4b89-ba57-5c0960eb305f
Expired
|
10.2 KB |
|
test_reports_7ad9bb8c-8d13-4050-88a7-4af007e31669
Expired
|
34.6 KB |
|
test_reports_7faae04c-9244-491f-985f-2342ca432c20
Expired
|
8.26 KB |
|
test_reports_890f4567-0869-419f-836d-fca8776bbab8
Expired
|
1.17 KB |
|
test_reports_e1e9acd0-924d-4313-8597-266b3f0f7ffc
Expired
|
4.94 KB |
|
test_reports_f0a934e4-14f3-4365-ad04-e6ef80c1d803
Expired
|
7.18 KB |
|