Blackhole post-commit tests #1071
ttmchioublackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
47s
static-checks
/
check-spdx-licenses
50s
static-checks
/
check-metal-kernel-count
5s
static-checks
/
check-black
36s
static-checks
/
check-doc
14s
static-checks
/
check-forbidden-imports
6s
static-checks
/
check-sweeps-workflow
10s
umd-unit-tests
/
blackhole BH
46m 58s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
11m 25s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
23 errors and 3 warnings
|
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 / 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.
|
|
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.
|
|
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 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 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 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.
|
|
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.
|
|
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 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.
|
|
fd-unit-tests / eager unit tests 7 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/20241008125319_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_29054681-d8a3-41a4-84f3-7631921d9670
Expired
|
8.21 KB |
|
|
test_reports_3c91e8e6-3f78-4925-b301-32efb59eed2b
Expired
|
3.8 KB |
|
|
test_reports_491f1042-2cde-4494-a77c-445cca1410aa
Expired
|
871 Bytes |
|
|
test_reports_60ebe490-3633-4534-bbc1-4c72f70c2514
Expired
|
9.22 KB |
|
|
test_reports_6c15a25d-fa1d-4e14-a7ae-eff090ed98c3
Expired
|
10.4 KB |
|
|
test_reports_7cfb819d-4c1a-405e-983c-b7252625686f
Expired
|
36.2 KB |
|
|
test_reports_a562fb26-bd5a-49ef-b7e7-343e7d654e34
Expired
|
7.07 KB |
|
|
test_reports_fa168586-17ab-4b94-9a85-a5ff64e22162
Expired
|
4.94 KB |
|