Add support for max_new_tokens parameter #1245

Sign in to view logs

Triggered via push October 10, 2024 02:13

goliaro

inference

Status Failure

Total duration 1d 10h 49m 16s

Artifacts –

docker-build.yml

on: push

Start an AWS instance to build the ROCM Docker images

Matrix: Build and Install FlexFlow in a Docker Container (CUDA backend)

Build and Install FlexFlow in a Docker Container (ROCm backend)

Matrix: Build and Deploy FlexFlow Docker Containers (ROCm backend)

Keep runner alive

Notify Slack in case of failure

Stop the AWS instance we used to build the ROCM Docker images

Annotations

11 errors and 13 warnings

Build and Install FlexFlow in a Docker Container (CUDA backend) (11.7)

Process completed with exit code 1.

Build and Install FlexFlow in a Docker Container (CUDA backend) (11.1)

Process completed with exit code 1.

Build and Install FlexFlow in a Docker Container (CUDA backend) (11.6)

Process completed with exit code 1.

Build and Install FlexFlow in a Docker Container (CUDA backend) (11.8)

Process completed with exit code 1.

Build and Install FlexFlow in a Docker Container (CUDA backend) (12.2)

Process completed with exit code 1.

Build and Install FlexFlow in a Docker Container (CUDA backend) (12.0)

Process completed with exit code 1.

Build and Install FlexFlow in a Docker Container (CUDA backend) (12.1)

Process completed with exit code 1.

Build and Deploy FlexFlow Docker Containers (ROCm backend) (5.4)

This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.

Build and Deploy FlexFlow Docker Containers (ROCm backend) (5.3)

This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.

Build and Deploy FlexFlow Docker Containers (ROCm backend) (5.5)

This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.

Build and Deploy FlexFlow Docker Containers (ROCm backend) (5.6)

This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.

Start an AWS instance to build the ROCM Docker images

The following actions uses node12 which is deprecated and will be forced to run on node16: aws-actions/configure-aws-credentials@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Start an AWS instance to build the ROCM Docker images

The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Start an AWS instance to build the ROCM Docker images

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Build and Install FlexFlow in a Docker Container (CUDA backend) (11.7)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Build and Install FlexFlow in a Docker Container (CUDA backend) (11.1)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Build and Install FlexFlow in a Docker Container (CUDA backend) (11.6)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Build and Install FlexFlow in a Docker Container (CUDA backend) (11.8)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Build and Install FlexFlow in a Docker Container (CUDA backend) (12.2)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Build and Install FlexFlow in a Docker Container (CUDA backend) (12.0)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Build and Install FlexFlow in a Docker Container (CUDA backend) (12.1)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Stop the AWS instance we used to build the ROCM Docker images

The following actions uses node12 which is deprecated and will be forced to run on node16: aws-actions/configure-aws-credentials@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Stop the AWS instance we used to build the ROCM Docker images

The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Stop the AWS instance we used to build the ROCM Docker images

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/