Blackhole post-commit tests #1065
blackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
19s
static-checks
/
check-spdx-licenses
54s
static-checks
/
check-metal-kernel-count
7s
static-checks
/
check-black
41s
static-checks
/
check-doc
12s
static-checks
/
check-forbidden-imports
7s
static-checks
/
check-sweeps-workflow
17s
umd-unit-tests
/
blackhole BH
46m 54s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
11m 26s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
24 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 / ttnn ccl cpp unit tests 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.
|
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 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 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 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 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 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.
|
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.
|
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
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/20241008004958_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_655b4afd-e5b6-4d7a-bcd6-5764639d4eb0
Expired
|
10.2 KB |
|
test_reports_66f0c481-f2f5-417a-ae8f-3895e0602482
Expired
|
9.32 KB |
|
test_reports_77f3c673-5103-4c5c-9824-754fcfa2237a
Expired
|
8.24 KB |
|
test_reports_995ff0e7-f012-4720-9393-cfecc1281485
Expired
|
3.79 KB |
|
test_reports_b0e494f3-b873-4446-a8b5-449b31f6e1d7
Expired
|
34.7 KB |
|
test_reports_cc5d1325-cd2f-41d4-a277-38c1b8fca136
Expired
|
5.64 KB |
|
test_reports_d41c53fc-a0c8-4302-a28e-97348151a7bb
Expired
|
873 Bytes |
|
test_reports_f16398eb-ec59-4485-aa65-1ed8cb913d55
Expired
|
4.94 KB |
|
test_reports_f369d2cc-8f7c-45eb-94d0-dedbd55422b4
Expired
|
7.16 KB |
|