Blackhole post-commit tests #1232
blackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
16s
static-checks
/
check-spdx-licenses
48s
static-checks
/
check-metal-kernel-count
6s
static-checks
/
check-black
26s
static-checks
/
check-doc
14s
static-checks
/
check-forbidden-imports
6s
static-checks
/
check-sweeps-workflow
8s
static-checks
/
clang-tidy
0s
umd-unit-tests
/
blackhole BH
1m 9s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
14m 35s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
9 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 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.
|
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.
|
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 / ttnn ccl cpp 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 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.
|
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 6 blackhole BH
No files were found with the provided path: ~/run-log/20241020103841_sys_logs.tar. No artifacts will be uploaded.
|
fd-unit-tests / eager unit tests 5 blackhole BH
No files were found with the provided path: ~/run-log/20241020104314_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_0e7e5ec2-df42-48eb-a369-0fca2f99e8f8
Expired
|
9.26 KB |
|
test_reports_7153255e-4c1b-4160-961a-b8ef9c26fb4c
Expired
|
4.88 KB |
|
test_reports_7fc74227-4a4d-4ce9-93f6-88bf6716b272
Expired
|
4.48 KB |
|
test_reports_a3eb9122-67a1-4800-a094-f58bdba7065d
Expired
|
36.1 KB |
|
test_reports_aeef9ed9-9083-4dfb-8c26-19604a217c74
Expired
|
6.84 KB |
|
test_reports_af4fde79-42f8-4a95-9df7-0d8d9adc8b1e
Expired
|
869 Bytes |
|
test_reports_c104ab4c-7958-4d3e-bf0d-74ef187a5082
Expired
|
9.51 KB |
|
test_reports_dbf50e89-38f4-4500-992f-a2f2def57ad2
Expired
|
8.47 KB |
|