Blackhole post-commit tests #1098
ttmchioublackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
18s
static-checks
/
check-spdx-licenses
53s
static-checks
/
check-metal-kernel-count
7s
static-checks
/
check-black
40s
static-checks
/
check-doc
13s
static-checks
/
check-forbidden-imports
5s
static-checks
/
check-sweeps-workflow
10s
umd-unit-tests
/
blackhole BH
44m 59s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
44m 58s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
14 errors and 2 warnings
|
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.
|
|
sd-unit-tests / blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh02 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.
|
|
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.
|
|
cpp-unit-tests / C++ 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.
|
|
cpp-unit-tests / ttnn cpp tests blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh02 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 2 blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh01 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 3 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-gh02 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-gh01 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 5 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 7 blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh02 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 trace tests 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 / 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.
|
|
fd-unit-tests / eager unit tests 1 blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh01 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.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
TTMetal_build_blackhole
Expired
|
47 MB |
|
|
eager-dist-ubuntu-20.04-blackhole
Expired
|
371 MB |
|