Blackhole post-commit tests #1067
blackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
19s
static-checks
/
check-spdx-licenses
52s
static-checks
/
check-metal-kernel-count
6s
static-checks
/
check-black
42s
static-checks
/
check-doc
15s
static-checks
/
check-forbidden-imports
8s
static-checks
/
check-sweeps-workflow
11s
umd-unit-tests
/
blackhole BH
2h 8m
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
11m 22s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
21 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.
|
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 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.
|
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 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 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 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 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.
|
umd-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.
|
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/20241008044420_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_4b291e1d-5793-47f0-bb00-9795dcb7c529
Expired
|
8.24 KB |
|
test_reports_54e893d6-ebe4-4a4b-a904-ed37970f9eab
Expired
|
10.2 KB |
|
test_reports_5f6e6304-76bb-4679-a8f3-9376a0d565d1
Expired
|
5.66 KB |
|
test_reports_77e40b25-a7f4-4e75-80a0-aeeb1a148868
Expired
|
876 Bytes |
|
test_reports_7eb0450d-9da4-49c6-ab75-7f47aad72d1b
Expired
|
3.79 KB |
|
test_reports_c234a12b-3fe2-4949-9cb2-167cb0814edb
Expired
|
7.09 KB |
|
test_reports_cf77ffc1-19e8-4c19-ac19-4dc23eba7544
Expired
|
9.19 KB |
|
test_reports_d0ab258b-92f2-44f0-bd0a-f05398a75307
Expired
|
4.93 KB |
|
test_reports_f82c0125-79c2-4b4e-9126-5af293d97f2c
Expired
|
36.3 KB |
|