Skip to content

chore: link spans to parent #938

chore: link spans to parent

chore: link spans to parent #938

Triggered via push November 25, 2024 05:35
Status Failure
Total duration 16m 4s
Artifacts 1
Escape commit message to send in slack
0s
Escape commit message to send in slack
Deploy backend to AWS Elastic Beanstalk  /  set_environment
0s
Deploy backend to AWS Elastic Beanstalk / set_environment
Deploy worker to AWS Elastic Container Service  /  set_environment
0s
Deploy worker to AWS Elastic Container Service / set_environment
Deploy frontend to AWS Amplify  /  deploy-frontend
5m 58s
Deploy frontend to AWS Amplify / deploy-frontend
Deploy backend to AWS Elastic Beanstalk  /  lint-test
3m 37s
Deploy backend to AWS Elastic Beanstalk / lint-test
Deploy worker to AWS Elastic Container Service  /  lint
1m 6s
Deploy worker to AWS Elastic Container Service / lint
Send slack message when deployment starts
3s
Send slack message when deployment starts
Deploy backend to AWS Elastic Beanstalk  /  build_application
2m 7s
Deploy backend to AWS Elastic Beanstalk / build_application
Deploy worker to AWS Elastic Container Service  /  build_application
46s
Deploy worker to AWS Elastic Container Service / build_application
Deploy backend to AWS Elastic Beanstalk  /  deploy_backend
7m 59s
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Deploy backend to AWS Elastic Beanstalk  /  deploy_callback
8m 25s
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Deploy worker to AWS Elastic Container Service  /  deploy_sending
12m 28s
Deploy worker to AWS Elastic Container Service / deploy_sending
Deploy worker to AWS Elastic Container Service  /  deploy_logging
4m 31s
Deploy worker to AWS Elastic Container Service / deploy_logging
End-to-end Test  /  set_environment
0s
End-to-end Test / set_environment
End-to-end Test  /  playwright-run
54s
End-to-end Test / playwright-run
Send Slack message about failed build and tag engineers if it's prod
2s
Send Slack message about failed build and tag engineers if it's prod
Send Slack message about successful build
0s
Send Slack message about successful build
Fit to window
Zoom out
Zoom in

Annotations

1 error and 43 warnings
End-to-end Test / playwright-run
Process completed with exit code 1.
Send slack message when deployment starts
The following actions use a deprecated Node.js version and will be forced to run on node20: slackapi/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy worker to AWS Elastic Container Service / lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy worker to AWS Elastic Container Service / build_application
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, aws-actions/configure-aws-credentials@v2, aws-actions/amazon-ecr-login@v1, docker/setup-buildx-action@v2, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy backend to AWS Elastic Beanstalk / lint-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy backend to AWS Elastic Beanstalk / build_application
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, aws-actions/configure-aws-credentials@v2, aws-actions/amazon-ecr-login@v1, docker/setup-buildx-action@v2, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy frontend to AWS Amplify / deploy-frontend
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, aws-actions/configure-aws-credentials@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy worker to AWS Elastic Container Service / deploy_logging
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'compatibilities' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'taskDefinitionArn' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'requiresAttributes' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'revision' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'registeredAt' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'registeredBy' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy backend to AWS Elastic Beanstalk / deploy_backend
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2, einaregilsson/beanstalk-deploy@v21. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment update finished, but health is Red and health status is Degraded. Giving it 480 seconds to recover...
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment still has health: Red and health status Degraded. Waiting 459 more seconds before failing...
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment still has health: Red and health status Degraded. Waiting 438 more seconds before failing...
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment still has health: Red and health status Degraded. Waiting 417 more seconds before failing...
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment still has health: Red and health status Degraded. Waiting 396 more seconds before failing...
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment still has health: Red and health status Degraded. Waiting 375 more seconds before failing...
Deploy backend to AWS Elastic Beanstalk / deploy_callback
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2, einaregilsson/beanstalk-deploy@v21. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment update finished, but health is Red and health status is Degraded. Giving it 480 seconds to recover...
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 459 more seconds before failing...
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 438 more seconds before failing...
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 417 more seconds before failing...
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 397 more seconds before failing...
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 376 more seconds before failing...
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 355 more seconds before failing...
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 335 more seconds before failing...
Deploy worker to AWS Elastic Container Service / deploy_sending
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'compatibilities' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'taskDefinitionArn' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'requiresAttributes' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'revision' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'registeredAt' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'registeredBy' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
End-to-end Test / playwright-run
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/
Send Slack message about failed build and tag engineers if it's prod
The following actions use a deprecated Node.js version and will be forced to run on node20: slackapi/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
playwright-report
174 KB