Skip to content

(T3K) Choose your pipeline #151

(T3K) Choose your pipeline

(T3K) Choose your pipeline #151

Manually triggered November 20, 2024 23:35
Status Failure
Total duration 1d 2h 18m 20s
Artifacts 2

pipeline-select-t3k.yaml

on: workflow_dispatch
build-artifact  /  ...  /  build-docker-image
41s
build-artifact / build-docker-image / build-docker-image
Matrix: build-artifact / build-artifact
Matrix: t3000-demo-tests / t3000-demo-tests
Waiting for pending jobs
Matrix: t3000-frequent-tests / t3000-frequent-tests
Waiting for pending jobs
Matrix: t3000-model-perf-tests / t3000-model-perf-tests
Waiting for pending jobs
Matrix: t3000-nightly-tests / t3000-nightly-tests
Waiting for pending jobs
Matrix: t3000-profiler-tests / t3000-profiler-tests
Waiting for pending jobs
Matrix: t3000-unit-tests / t3000-unit-tests
Fit to window
Zoom out
Zoom in

Annotations

17 errors and 7 notices
t3000-unit-tests / t3k grok tests
The job running on runner tt-metal-ci-vm-t3k-02 has exceeded the maximum execution time of 360 minutes.
t3000-unit-tests / t3k falcon40b tests
The job running on runner tt-metal-ci-vm-t3k-02 has exceeded the maximum execution time of 360 minutes.
t3000-unit-tests / t3k falcon7b tests
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
t3000-unit-tests / t3k falcon7b tests
Process completed with exit code 1.
t3000-unit-tests / t3k falcon7b tests
A task was canceled.
t3000-unit-tests / t3k llama3.2-11b tests
The self-hosted runner: tt-metal-ci-vm-t3k-02 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.
t3000-unit-tests / t3k llama3.1-70b tests
Process completed with exit code 1.
t3000-unit-tests / t3k llama3.1-70b tests
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
t3000-unit-tests / t3k llama3.2-11b-vision tests
The self-hosted runner: tt-metal-ci-vm-t3k-02 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.
t3000-unit-tests / t3k llama3-small tests
The self-hosted runner: tt-metal-ci-vm-t3k-02 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.
t3000-unit-tests / t3k mixtral tests
The job running on runner tt-metal-ci-vm-t3k-02 has exceeded the maximum execution time of 360 minutes.
t3000-unit-tests / t3k n300 mesh llama3.2-11b-vision tests
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
t3000-unit-tests / t3k n300 mesh llama3.2-11b-vision tests
Process completed with exit code 1.
t3000-unit-tests / t3k n300 mesh llama3.2-11b-vision tests
A task was canceled.
t3000-unit-tests / t3k ttmetal tests
The self-hosted runner: tt-metal-ci-vm-t3k-02 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.
t3000-unit-tests / t3k ttnn tests
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
t3000-unit-tests / t3k unet shallow tests
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
disk-usage-before-startup
Disk usage is 94 %
disk-usage-after-startup
Disk usage is 94 %
printing-smi-info-startup
Touching and printing out SMI info
reset-successful-startup
tt-smi reset was successful
printing-out-smi-info-cleanup
Touching and printing out SMI info
successful-reset-cleanup
tt-smi reset was successful
reset-successful-cleanup
tt-smi reset was successful

Artifacts

Produced during runtime
Name Size
TTMetal_build_grayskull Expired
299 MB
TTMetal_build_wormhole_b0 Expired
299 MB