Blackhole post-commit tests #1237
ttmchioublackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
16s
static-checks
/
check-spdx-licenses
48s
static-checks
/
check-metal-kernel-count
4s
static-checks
/
check-black
26s
static-checks
/
check-doc
13s
static-checks
/
check-forbidden-imports
6s
static-checks
/
check-sweeps-workflow
7s
static-checks
/
clang-tidy
0s
umd-unit-tests
/
blackhole BH
43m 34s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
13m 26s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
9 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 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.
|
|
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 6 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.
|
|
fd-unit-tests / eager unit tests 4 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/20241020183639_sys_logs.tar. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
TTMetal_build_blackhole
Expired
|
46.9 MB |
|
|
eager-dist-ubuntu-20.04-blackhole
Expired
|
372 MB |
|
|
test_reports_2bb9a33a-c46d-4b56-8097-a43e8011945e
Expired
|
36 KB |
|
|
test_reports_2e106d26-bd0b-4569-a58a-d89ef1798e98
Expired
|
4.48 KB |
|
|
test_reports_3ea1f764-6a16-4bd1-b0d5-66ad83efb274
Expired
|
870 Bytes |
|
|
test_reports_84925513-e011-4806-bc2c-f4dddfc1fa40
Expired
|
9.47 KB |
|
|
test_reports_8f188d72-595d-4e1f-bf59-727e614b1297
Expired
|
9.16 KB |
|
|
test_reports_9c8e1732-1d4a-4025-aaf1-c66dbc441d2c
Expired
|
6.81 KB |
|
|
test_reports_e046fbd1-0079-46b9-a82c-9089408512cc
Expired
|
8.44 KB |
|
|
test_reports_ee4454a5-7e0b-4848-8e43-15bca0531dfc
Expired
|
4.87 KB |
|