Blackhole post-commit tests #1028
blackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
46s
static-checks
/
check-spdx-licenses
53s
static-checks
/
check-metal-kernel-count
6s
static-checks
/
check-black
38s
static-checks
/
check-doc
12s
static-checks
/
check-forbidden-imports
6s
static-checks
/
check-sweeps-workflow
7s
umd-unit-tests
/
blackhole BH
1m 39s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
11m 19s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
24 errors and 4 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.
|
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 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.
|
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.
|
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 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 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.
|
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.
|
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.
|
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/20241005042937_sys_logs.tar. No artifacts will be uploaded.
|
fd-unit-tests / eager unit tests 7 blackhole BH
No files were found with the provided path: ~/run-log/20241005043100_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_133510d4-f602-4dc2-892a-fd380b524ff9
Expired
|
1.17 KB |
|
test_reports_75a20760-a925-43ce-8901-15d61f4e0615
Expired
|
7.17 KB |
|
test_reports_78b75040-5f81-44ad-91ff-eed4718bc5e8
Expired
|
10.2 KB |
|
test_reports_8d1709c5-0cb6-44d1-9fb5-087e81c092da
Expired
|
8.28 KB |
|
test_reports_8e02cc96-009d-44a8-a3fb-7e8474de696c
Expired
|
875 Bytes |
|
test_reports_952b32b6-7bce-4c05-8883-56c631938236
Expired
|
35 KB |
|
test_reports_a5c7c185-4fdf-4bd2-89da-346a5e9abaa1
Expired
|
3.86 KB |
|
test_reports_baee7f32-3e39-414c-82aa-23680391d24c
Expired
|
4.94 KB |
|
test_reports_f662e8a0-476e-4484-9a97-8ec52128e3ee
Expired
|
9.28 KB |
|