Skip to content
Create EKS cluster, deploy MLflow and run bundle test

Create EKS cluster, deploy CKF and MLflow and run MLflow bundle UATs #23

Sign in to view logs

Create EKS cluster, deploy CKF and MLflow and run MLflow bundle UATs

Create EKS cluster, deploy CKF and MLflow and run MLflow bundle UATs #23

Triggered via schedule January 16, 2024 00:36
@misohumisohu
⁠ 79e6559
main
Status Failure
Total duration 44s
Artifacts –

deploy-eks.yaml

on: schedule
deploy-mlflow-to-eks
20s
deploy-mlflow-to-eks
delete-unattached-volumes  /  delete-volumes
7s
delete-unattached-volumes / delete-volumes
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 2 warnings
deploy-mlflow-to-eks
Process completed with exit code 1.
deploy-mlflow-to-eks
Process completed with exit code 1.
deploy-mlflow-to-eks
Process completed with exit code 127.
deploy-mlflow-to-eks
Process completed with exit code 1.
deploy-mlflow-to-eks
Process completed with exit code 252.
deploy-mlflow-to-eks
Process completed with exit code 127.
delete-unattached-volumes / delete-volumes
Process completed with exit code 252.
deploy-mlflow-to-eks
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
delete-unattached-volumes / delete-volumes
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/