Skip to content
Build and Test

Runners #333

Sign in to view logs

Runners

Runners #333

Triggered via pull request December 17, 2024 21:03
@AlexCheemaAlexCheema
synchronize #546
runners
Status Cancelled
Total duration 1d 0h 12m 9s
Artifacts –

benchmarks.yml

on: pull_request
Matrix: single-m4-pro
Matrix: test-m3-single-node
Matrix: three-m4-pro-cluster
Matrix: two-m4-pro-cluster
Fit to window
Zoom out
Zoom in

Annotations

30 errors and 11 warnings
three-m4-pro-cluster (llama-3.2-3b) / run-distributed-job (M4PRO_GPU16_24GB)
Process completed with exit code 1.
three-m4-pro-cluster (llama-3.2-3b) / run-distributed-job (M4PRO_GPU16_24GB)
The job was canceled because "M4PRO_GPU16_24GB" failed.
three-m4-pro-cluster (llama-3.2-3b) / run-distributed-job (M4PRO_GPU16_24GB)
The operation was canceled.
three-m4-pro-cluster (llama-3.2-3b) / run-distributed-job (M4PRO_GPU16_24GB)
The job was canceled because "M4PRO_GPU16_24GB" failed.
three-m4-pro-cluster (llama-3.2-3b) / run-distributed-job (M4PRO_GPU16_24GB)
The operation was canceled.
two-m4-pro-cluster (llama-3.1-8b) / run-distributed-job (M4PRO_GPU16_24GB)
Process completed with exit code 1.
two-m4-pro-cluster (llama-3.1-8b) / run-distributed-job (M4PRO_GPU16_24GB)
The job was canceled because "M4PRO_GPU16_24GB" failed.
two-m4-pro-cluster (llama-3.1-8b) / run-distributed-job (M4PRO_GPU16_24GB)
The operation was canceled.
two-m4-pro-cluster (llama-3.2-1b) / run-distributed-job (M4PRO_GPU16_24GB)
FailFast: cancelling since parallel instance has failed
two-m4-pro-cluster (llama-3.2-1b) / run-distributed-job (M4PRO_GPU16_24GB)
FailFast: cancelling since parallel instance has failed
two-m4-pro-cluster (llama-3.2-3b) / run-distributed-job (M4PRO_GPU16_24GB)
FailFast: cancelling since parallel instance has failed
two-m4-pro-cluster (llama-3.2-3b) / run-distributed-job (M4PRO_GPU16_24GB)
Process completed with exit code 1.
two-m4-pro-cluster (llama-3.2-3b) / run-distributed-job (M4PRO_GPU16_24GB)
FailFast: cancelling since parallel instance has failed
two-m4-pro-cluster (llama-3.2-3b) / run-distributed-job (M4PRO_GPU16_24GB)
The operation was canceled.
three-m4-pro-cluster (llama-3.1-8b) / run-distributed-job (M4PRO_GPU16_24GB)
Process completed with exit code 1.
three-m4-pro-cluster (llama-3.1-8b) / run-distributed-job (M4PRO_GPU16_24GB)
The job was canceled because "M4PRO_GPU16_24GB_2" failed.
three-m4-pro-cluster (llama-3.1-8b) / run-distributed-job (M4PRO_GPU16_24GB)
The operation was canceled.
three-m4-pro-cluster (llama-3.1-8b) / run-distributed-job (M4PRO_GPU16_24GB)
The job was canceled because "M4PRO_GPU16_24GB_2" failed.
three-m4-pro-cluster (llama-3.1-8b) / run-distributed-job (M4PRO_GPU16_24GB)
The operation was canceled.
three-m4-pro-cluster (llama-3.2-1b) / run-distributed-job (M4PRO_GPU16_24GB)
Process completed with exit code 1.
three-m4-pro-cluster (llama-3.2-1b) / run-distributed-job (M4PRO_GPU16_24GB)
The job was canceled because "M4PRO_GPU16_24GB" failed.
three-m4-pro-cluster (llama-3.2-1b) / run-distributed-job (M4PRO_GPU16_24GB)
The operation was canceled.
three-m4-pro-cluster (llama-3.2-1b) / run-distributed-job (M4PRO_GPU16_24GB)
The job was canceled because "M4PRO_GPU16_24GB" failed.
three-m4-pro-cluster (llama-3.2-1b) / run-distributed-job (M4PRO_GPU16_24GB)
The operation was canceled.
three-m4-pro-cluster (llama-3.3-70b) / run-distributed-job (M4PRO_GPU16_24GB)
Process completed with exit code 1.
three-m4-pro-cluster (llama-3.3-70b) / run-distributed-job (M4PRO_GPU16_24GB)
The job was canceled because "M4PRO_GPU16_24GB" failed.
three-m4-pro-cluster (llama-3.3-70b) / run-distributed-job (M4PRO_GPU16_24GB)
The operation was canceled.
three-m4-pro-cluster (llama-3.3-70b) / run-distributed-job (M4PRO_GPU16_24GB)
The job was canceled because "M4PRO_GPU16_24GB" failed.
three-m4-pro-cluster (llama-3.3-70b) / run-distributed-job (M4PRO_GPU16_24GB)
The operation was canceled.
test-m3-single-node (llama-3.2-1b) / run-distributed-job (M3MAX_GPU40_128GB)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
single-m4-pro (llama-3.1-8b) / generate-matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-m3-single-node (llama-3.2-1b) / generate-matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
three-m4-pro-cluster (llama-3.2-3b) / generate-matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
two-m4-pro-cluster (llama-3.1-8b) / generate-matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
single-m4-pro (llama-3.2-3b) / generate-matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
two-m4-pro-cluster (llama-3.2-3b) / generate-matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
single-m4-pro (llama-3.2-1b) / generate-matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
three-m4-pro-cluster (llama-3.1-8b) / generate-matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
three-m4-pro-cluster (llama-3.3-70b) / generate-matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
three-m4-pro-cluster (llama-3.2-1b) / generate-matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
two-m4-pro-cluster (llama-3.2-1b) / generate-matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636