Blackhole post-commit tests #1242
blackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
48s
static-checks
/
check-spdx-licenses
48s
static-checks
/
check-metal-kernel-count
5s
static-checks
/
check-black
27s
static-checks
/
check-doc
13s
static-checks
/
check-forbidden-imports
8s
static-checks
/
check-sweeps-workflow
7s
static-checks
/
clang-tidy
0s
umd-unit-tests
/
blackhole BH
43m 8s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
13m 37s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
13 errors and 3 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 3 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 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.
|
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.
|
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 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/20241021044347_sys_logs.tar. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
TTMetal_build_blackhole
|
47 MB |
|
eager-dist-ubuntu-20.04-blackhole
|
372 MB |
|
test_reports_22b585ff-c18d-40a5-bc51-a709289cb99f
|
4.48 KB |
|
test_reports_865e450c-dc4c-42f2-8653-1e4f8c953167
|
878 Bytes |
|
test_reports_924ff22f-2f16-4fb5-9bcd-663c55e62410
|
8.01 KB |
|
test_reports_b0845d86-1373-4d21-a17c-41fdb3ec2cd9
|
9.09 KB |
|
test_reports_c053d521-4a2c-4d44-b3e3-bcbf01f670fd
|
6.88 KB |
|
test_reports_de9e3332-f799-4db1-a795-667ec64e93a6
|
9.49 KB |
|
test_reports_ed268a62-3885-4d65-9cbf-b5adff9cd37f
|
9.3 KB |
|
test_reports_ffa1db8d-e0a8-40a2-af5b-eb7e56a10228
|
4.86 KB |
|