Skip to content

feat(router): explicit warning if revision is not set #942

feat(router): explicit warning if revision is not set

feat(router): explicit warning if revision is not set #942

Triggered via pull request July 13, 2023 16:49
Status Failure
Total duration 49s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

build.yaml

on: pull_request
Start self-hosted EC2 runner
28s
Start self-hosted EC2 runner
build-and-push-image
0s
build-and-push-image
integration-tests
0s
integration-tests
Stop self-hosted EC2 runner
4s
Stop self-hosted EC2 runner
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 14 warnings
Start self-hosted EC2 runner
Failed to launch instance after trying in 6 subnets.
Start self-hosted EC2 runner
AWS EC2 instance undefined initialization error
Start self-hosted EC2 runner
ResourceNotReady: Resource is not in the state instanceRunning
Start self-hosted EC2 runner
Resource is not in the state instanceRunning
Stop self-hosted EC2 runner
Error: Not all the required inputs are provided for the 'stop' mode
Stop self-hosted EC2 runner
Not all the required inputs are provided for the 'stop' mode
Stop self-hosted EC2 runner
TypeError: Cannot read properties of undefined (reading 'mode')
Stop self-hosted EC2 runner
Cannot read properties of undefined (reading 'mode')
Start self-hosted EC2 runner
The following actions uses node12 which is deprecated and will be forced to run on node16: aws-actions/configure-aws-credentials@v1, philschmid/philschmid-ec2-github-runner@main. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Start self-hosted EC2 runner
AWS EC2 instance starting error
Start self-hosted EC2 runner
InsufficientInstanceCapacity: We currently do not have sufficient g5.12xlarge capacity in the Availability Zone you requested (us-east-1a). Our system will be working on provisioning additional capacity. You can currently get g5.12xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-1b, us-east-1c, us-east-1d, us-east-1f.
Start self-hosted EC2 runner
AWS EC2 instance starting error
Start self-hosted EC2 runner
InsufficientInstanceCapacity: We currently do not have sufficient g5.12xlarge capacity in the Availability Zone you requested (us-east-1b). Our system will be working on provisioning additional capacity. You can currently get g5.12xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-1a, us-east-1c, us-east-1d, us-east-1f.
Start self-hosted EC2 runner
AWS EC2 instance starting error
Start self-hosted EC2 runner
InsufficientInstanceCapacity: We currently do not have sufficient g5.12xlarge capacity in the Availability Zone you requested (us-east-1c). Our system will be working on provisioning additional capacity. You can currently get g5.12xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-1a, us-east-1b, us-east-1d, us-east-1f.
Start self-hosted EC2 runner
AWS EC2 instance starting error
Start self-hosted EC2 runner
InsufficientInstanceCapacity: We currently do not have sufficient g5.12xlarge capacity in the Availability Zone you requested (us-east-1d). Our system will be working on provisioning additional capacity. You can currently get g5.12xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-1a, us-east-1b, us-east-1c, us-east-1f.
Start self-hosted EC2 runner
AWS EC2 instance starting error
Start self-hosted EC2 runner
Unsupported: Your requested instance type (g5.12xlarge) is not supported in your requested Availability Zone (us-east-1e). Please retry your request by not specifying an Availability Zone or choosing us-east-1a, us-east-1b, us-east-1c, us-east-1d, us-east-1f.
Start self-hosted EC2 runner
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/
Stop self-hosted EC2 runner
The following actions uses node12 which is deprecated and will be forced to run on node16: aws-actions/configure-aws-credentials@v1, philschmid/philschmid-ec2-github-runner@main. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Stop self-hosted EC2 runner
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/