Blackhole post-commit tests #3778
ttmchioublackhole-post-commit.yaml
on: workflow_dispatch
build-artifact-profiler
/
...
/
check-docker-images
9s
build-artifact
/
...
/
check-docker-images
7s
static-checks
/
Run Pre-commit Hooks
27s
static-checks
/
check-black
1s
static-checks
/
check-spdx-licenses
52s
static-checks
/
check-metal-kernel-count
7s
static-checks
/
check-doc
19s
static-checks
/
check-docs-links
13s
static-checks
/
check-forbidden-imports
5s
static-checks
/
check-sweeps-workflow
12s
static-checks
/
cmake-version
14s
umd-unit-tests
/
blackhole P150-194
1m 6s
build-artifact-profiler
/
...
/
🐳️ Build image
0s
build-artifact-profiler
/
🛠️ Build Release ubuntu 20.04
4m 43s
build-artifact
/
🛠️ Build Release ubuntu 22.04
5m 12s
run-profiler-regression
/
profiler-regression
12m 43s
Matrix: cpp-unit-tests / cpp-unit-tests
Matrix: fd-unit-tests / fd-tests
Matrix: sd-unit-tests / cpp-unit-tests-slow-dispatch
Annotations
40 errors, 3 warnings, and 109 notices
|
umd-unit-tests / blackhole P150-194
unable to access 'https://github.com/tenstorrent/tt-llk.git/': The requested URL returned error: 400
|
|
umd-unit-tests / blackhole P150-194
unable to access 'https://github.com/tenstorrent/tt-llk.git/': The requested URL returned error: 400
|
|
umd-unit-tests / blackhole P150-194
The process '/usr/bin/git' failed with exit code 1
|
|
run-profiler-regression / profiler-regression
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194 All C++
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194 api
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194 debug_tools
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194 dispatch
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194 device
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194 distributed
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194 eth
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194 FD2
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194 llk
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194 stl
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194 tools
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194 user kernel path
The self-hosted runner: tt-metal-ci-vm-194 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 / All C++ blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 / api blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 / debug_tools blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 / device blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 / dispatch multicmd queue blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 / dispatch blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 / distributed blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 / eth blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 / lightmetal blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 / llk blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 / stl blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 / tools blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 unit tests blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 tensor cpp unit tests blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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 / user kernel path blackhole P150-194
The self-hosted runner: tt-metal-ci-vm-194 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.
|
|
static-checks / Run Pre-commit Hooks
Unexpected input(s) 'fetch-refs', valid inputs are ['repository', 'ref', 'token', 'ssh-key', 'ssh-known-hosts', 'ssh-strict', 'ssh-user', 'persist-credentials', 'path', 'clean', 'filter', 'sparse-checkout', 'sparse-checkout-cone-mode', 'fetch-depth', 'fetch-tags', 'show-progress', 'lfs', 'submodules', 'set-safe-directory', 'github-server-url']
|
|
static-checks / Run Pre-commit Hooks
Unexpected input(s) 'fetch-refs', valid inputs are ['repository', 'ref', 'token', 'ssh-key', 'ssh-known-hosts', 'ssh-strict', 'ssh-user', 'persist-credentials', 'path', 'clean', 'filter', 'sparse-checkout', 'sparse-checkout-cone-mode', 'fetch-depth', 'fetch-tags', 'show-progress', 'lfs', 'submodules', 'set-safe-directory', 'github-server-url']
|
|
hugepages-service-not-found-startup
Hugepages service not found. Using old rc.local method
|
|
disk-usage-after-startup
Disk usage is 53 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
reset-successful-startup
tt-smi reset was successful
|
|
hugepages-setup-success-startup
Hugepages is now setup.
|
|
printing-out-smi-info-cleanup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 35 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
attempting-reset-startup
Attempting to reset card(s). Sleeping first
|
|
reset-successful-startup
tt-smi reset was successful
|
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
|
hugepages-setup-success-startup
Hugepages is now setup.
|
|
disk-usage-after-startup
Disk usage is 34 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
attempting-reset-startup
Attempting to reset card(s). Sleeping first
|
|
reset-successful-startup
tt-smi reset was successful
|
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
|
hugepages-setup-success-startup
Hugepages is now setup.
|
|
disk-usage-after-startup
Disk usage is 35 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
attempting-reset-startup
Attempting to reset card(s). Sleeping first
|
|
reset-successful-startup
tt-smi reset was successful
|
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
|
hugepages-setup-success-startup
Hugepages is now setup.
|
|
disk-usage-after-startup
Disk usage is 38 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
attempting-reset-startup
Attempting to reset card(s). Sleeping first
|
|
reset-successful-startup
tt-smi reset was successful
|
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
|
hugepages-setup-success-startup
Hugepages is now setup.
|
|
disk-usage-after-startup
Disk usage is 38 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
attempting-reset-startup
Attempting to reset card(s). Sleeping first
|
|
reset-successful-startup
tt-smi reset was successful
|
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
|
hugepages-setup-success-startup
Hugepages is now setup.
|
|
disk-usage-after-startup
Disk usage is 39 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
attempting-reset-startup
Attempting to reset card(s). Sleeping first
|
|
reset-successful-startup
tt-smi reset was successful
|
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
|
hugepages-setup-success-startup
Hugepages is now setup.
|
|
disk-usage-after-startup
Disk usage is 39 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
attempting-reset-startup
Attempting to reset card(s). Sleeping first
|
|
reset-successful-startup
tt-smi reset was successful
|
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
|
hugepages-setup-success-startup
Hugepages is now setup.
|
|
disk-usage-after-startup
Disk usage is 39 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 39 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 40 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 40 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 40 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 40 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 41 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 41 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 41 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 41 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 42 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 42 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 42 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 42 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 43 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 43 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 43 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 43 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 44 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 44 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 44 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 45 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 45 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 45 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 45 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 46 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 46 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 46 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 46 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 47 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 47 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
TTMetal_build_any
|
186 MB |
|
|
TTMetal_build_any_profiler
|
191 MB |
|
|
eager-dist-ubuntu-22.04-any
|
333 MB |
|
|
packages-ubuntu-20.04-amd64-Release-x86_64-linux-clang-17-libcpp_profiler
|
89.5 MB |
|
|
packages-ubuntu-22.04-amd64-Release-x86_64-linux-clang-17-libcpp
|
89.4 MB |
|