Blackhole post-commit tests #1239
blackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
31s
static-checks
/
check-spdx-licenses
53s
static-checks
/
check-metal-kernel-count
6s
static-checks
/
check-black
26s
static-checks
/
check-doc
16s
static-checks
/
check-forbidden-imports
5s
static-checks
/
check-sweeps-workflow
7s
static-checks
/
clang-tidy
0s
umd-unit-tests
/
blackhole BH
44m 37s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
13m 32s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
9 errors and 4 warnings
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.
|
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 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 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 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 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 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.
|
umd-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 5 blackhole BH
No files were found with the provided path: ~/run-log/20241020223815_sys_logs.tar. No artifacts will be uploaded.
|
fd-unit-tests / eager unit tests 6 blackhole BH
No files were found with the provided path: ~/run-log/20241020224052_sys_logs.tar. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
TTMetal_build_blackhole
|
46.9 MB |
|
eager-dist-ubuntu-20.04-blackhole
|
372 MB |
|
test_reports_35cb8c76-723b-4196-95b2-97227445a137
|
9.45 KB |
|
test_reports_5f57effb-7c87-4ad8-b38d-0231ce7a391f
|
8.45 KB |
|
test_reports_60faff09-2f30-45a1-aedb-5105a57d336b
|
9.28 KB |
|
test_reports_7df7594c-5dc8-4314-acb2-080037772fd0
|
9.09 KB |
|
test_reports_81497bd0-6970-4b4c-a993-3e302b4a9d72
|
6.78 KB |
|
test_reports_86919338-5a66-46be-a03e-bdd7d811bbc0
|
36.1 KB |
|
test_reports_91f110a1-8b2c-44d7-9df8-bcfa48b3b917
|
4.83 KB |
|
test_reports_96e29fb0-299e-4cff-802e-7f88c274035b
|
4.48 KB |
|
test_reports_c0717097-0aed-42c3-ada9-5f15450165d2
|
876 Bytes |
|