Blackhole post-commit tests #1234
pgkellerblackhole-post-commit.yaml
on: workflow_dispatch
build-docker-image
/
build-docker-image
16s
static-checks
/
check-spdx-licenses
50s
static-checks
/
check-metal-kernel-count
6s
static-checks
/
check-black
25s
static-checks
/
check-doc
11s
static-checks
/
check-forbidden-imports
6s
static-checks
/
check-sweeps-workflow
9s
static-checks
/
clang-tidy
0s
umd-unit-tests
/
blackhole BH
45m 25s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
13m 34s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
12 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.
|
|
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 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 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 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 / 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 / eager unit tests 2 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/20241020145632_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_10776845-3b11-4744-861b-408727280954
|
8.03 KB |
|
|
test_reports_1ebc03b4-32c0-4dbb-8830-aaefb8063092
|
4.85 KB |
|
|
test_reports_28e893f1-73f6-475f-aecf-53968d00cc8f
|
9.45 KB |
|
|
test_reports_2cfd1110-d2a7-4ac1-a19c-7625d44f311f
|
876 Bytes |
|
|
test_reports_38561054-03b5-4054-b222-06c0f849d284
|
6.81 KB |
|
|
test_reports_c4d11321-a9fe-45a1-b94d-80351ff2af39
|
9.24 KB |
|
|
test_reports_d7cf84b2-e18a-488b-a23f-f84fe175b537
|
34.8 KB |
|
|
test_reports_dad98bfc-ff8f-4811-aa6e-07e1c2fc657b
|
9.1 KB |
|