Blackhole post-commit tests #1077
rdjogoTTblackhole-post-commit.yaml
on: workflow_dispatch
build-docker-image
/
build-docker-image
15s
static-checks
/
check-spdx-licenses
53s
static-checks
/
check-metal-kernel-count
8s
static-checks
/
check-black
40s
static-checks
/
check-doc
16s
static-checks
/
check-forbidden-imports
4s
static-checks
/
check-sweeps-workflow
10s
umd-unit-tests
/
blackhole BH
44m 58s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
12m 19s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
24 errors and 5 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.
|
|
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 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 / 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 5 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.
|
|
umd-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.
|
|
cpp-unit-tests / C++ 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.
|
|
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.
|
|
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-docker-image / build-docker-image
Unable to find merge base between 05709f423aa713fd299f52f4779d09e791a3228e and ea1149109d9a530290936790c6620f9f99263f4e
|
|
build-docker-image / build-docker-image
Set 'fetch_additional_submodule_history: true' to fetch additional submodule history for: tt_metal/third_party/tt_llk_blackhole
|
|
build-wheels / build-wheel
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
build-wheels / build-wheel
Cache paths are empty. Please check the previous logs and make sure that the python version is specified
|
|
fd-unit-tests / eager unit tests 6 blackhole BH
No files were found with the provided path: ~/run-log/20241008220521_sys_logs.tar. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
test_reports_02744c58-c2df-4c83-b39b-9177259597af
Expired
|
4.94 KB |
|
|
test_reports_1390cd7a-dced-427b-b860-071e33b19524
Expired
|
875 Bytes |
|
|
test_reports_450bc8c8-9d0b-4804-8d0d-0192de72bb3a
Expired
|
8.22 KB |
|
|
test_reports_68a573f0-1209-4787-abdc-541d0db9b396
Expired
|
12.6 KB |
|
|
test_reports_68b6226e-a296-471d-b69f-1b591a513f1b
Expired
|
5.66 KB |
|
|
test_reports_6e2cbe50-5ede-4ab6-90ca-cc4046a03fa5
Expired
|
9.27 KB |
|
|
test_reports_74c0006c-6bce-4053-a7e5-55be0509e32d
Expired
|
10.4 KB |
|
|
test_reports_87fb6290-95ac-4747-a5c8-5dd74199a704
Expired
|
7.14 KB |
|
|
test_reports_9ec5d0de-0829-466f-ae51-5a58d318afa1
Expired
|
36.1 KB |
|