Blackhole post-commit tests #1070
blackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
46s
static-checks
/
check-spdx-licenses
50s
static-checks
/
check-metal-kernel-count
6s
static-checks
/
check-black
39s
static-checks
/
check-doc
13s
static-checks
/
check-forbidden-imports
5s
static-checks
/
check-sweeps-workflow
10s
umd-unit-tests
/
blackhole BH
43m 47s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
45m 50s
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 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.
|
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.
|
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 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 / 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.
|
sd-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.
|
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/20241008103229_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_4527d6b8-a341-4787-af21-b68f1ea058d7
Expired
|
5.65 KB |
|
test_reports_481b0159-89f9-401c-a57a-3d4a07c3de32
Expired
|
10.1 KB |
|
test_reports_69d1f9cf-59b2-49cd-9600-5c0ac89760b7
Expired
|
8.21 KB |
|
test_reports_8501dadd-4f57-487f-a188-7ee2b4a306ba
Expired
|
9.2 KB |
|
test_reports_9219b147-1395-4346-b589-3fd21bd6753e
Expired
|
3.74 KB |
|
test_reports_9278d39e-c257-4cec-a7a5-835e42a343dc
Expired
|
7.2 KB |
|
test_reports_9c278bbc-6d81-48d9-aedf-b185a2f462ca
Expired
|
35 KB |
|
test_reports_b1b59682-ebbb-44f2-8b7a-408510528c32
Expired
|
875 Bytes |
|
test_reports_f4932197-09b8-464d-947d-6ddd24a13a18
Expired
|
4.94 KB |
|