Blackhole post-commit tests #1076
blackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
1m 3s
static-checks
/
check-spdx-licenses
57s
static-checks
/
check-metal-kernel-count
5s
static-checks
/
check-black
40s
static-checks
/
check-doc
11s
static-checks
/
check-forbidden-imports
6s
static-checks
/
check-sweeps-workflow
8s
umd-unit-tests
/
blackhole BH
1m 40s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
12m 7s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
24 errors and 3 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.
|
umd-unit-tests / blackhole BH
The operation was 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 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.
|
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.
|
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.
|
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 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.
|
cpp-unit-tests / C++ 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/20241008185044_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_08db01a4-dab3-4cd5-92b4-d9909eab1805
Expired
|
7.18 KB |
|
test_reports_1fba7022-9ce8-47bc-8e9a-d62ab4ad10d0
Expired
|
5.63 KB |
|
test_reports_28805459-efeb-4f2e-b745-6c8f899620ca
Expired
|
10.2 KB |
|
test_reports_4a6baa90-b22c-42ee-a905-772b586f2742
Expired
|
3.79 KB |
|
test_reports_62f1cf64-a52b-48b8-9b7d-0952be582b9e
Expired
|
4.94 KB |
|
test_reports_94314c75-54ff-4d95-8dc7-77e00805b435
Expired
|
9.25 KB |
|
test_reports_a4d30eb2-26d2-4bd0-a35b-a8a229872649
Expired
|
873 Bytes |
|
test_reports_ddac73bf-6d9a-46e5-906d-a06eff6dfb6d
Expired
|
8.22 KB |
|
test_reports_eb81e8b7-00ce-4be6-8b0e-5f40c803755a
Expired
|
34.6 KB |
|