Blackhole post-commit tests #1033
blackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
45s
static-checks
/
check-spdx-licenses
48s
static-checks
/
check-metal-kernel-count
7s
static-checks
/
check-black
38s
static-checks
/
check-doc
13s
static-checks
/
check-forbidden-imports
5s
static-checks
/
check-sweeps-workflow
8s
umd-unit-tests
/
blackhole BH
1m 36s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
12m 19s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
24 errors and 4 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 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 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.
|
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.
|
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 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 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 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 / 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 / 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.
|
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
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/20241005142908_sys_logs.tar. No artifacts will be uploaded.
|
fd-unit-tests / eager unit tests 7 blackhole BH
No files were found with the provided path: ~/run-log/20241005143003_sys_logs.tar. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
TTMetal_build_blackhole
Expired
|
48.6 MB |
|
eager-dist-ubuntu-20.04-blackhole
Expired
|
371 MB |
|
test_reports_1f0cd47c-2e36-47fd-bb37-119af2095891
Expired
|
877 Bytes |
|
test_reports_3180f6cc-fc33-4fa3-b851-9a4486091c84
Expired
|
10.1 KB |
|
test_reports_6d2f6b71-dd9c-4a44-afef-a85f49e2e1c0
Expired
|
9.27 KB |
|
test_reports_74791706-3ad1-48e0-8fd3-6e91a5db0b52
Expired
|
4.94 KB |
|
test_reports_77a08515-7b8a-4308-abfb-b5dd2ae842c7
Expired
|
34.7 KB |
|
test_reports_839fdc19-5a43-4d8b-8fd5-ffe966d6814d
Expired
|
3.86 KB |
|
test_reports_def88014-0a16-4166-8cbd-4cc9ac15cec4
Expired
|
8.25 KB |
|
test_reports_ea356f1b-8b53-4fb0-b685-737a1aadd588
Expired
|
7.12 KB |
|
test_reports_ed0a5384-e04e-4841-ac8b-602438cae89a
Expired
|
1.17 KB |
|