Skip to content

E2E on AWS CUDA - Reenable discard_events_l0_inorder test #8117

E2E on AWS CUDA - Reenable discard_events_l0_inorder test

E2E on AWS CUDA - Reenable discard_events_l0_inorder test #8117

Triggered via workflow run August 2, 2024 12:24
@omarahmed1111omarahmed1111
completed 2321b3a
Status Failure
Total duration 6m 6s
Artifacts

sycl-linux-precommit-aws.yml

on: workflow_run
aws-start
13s
aws-start
create-check
4s
create-check
e2e-cuda  /  run
e2e-cuda / run
aws-stop
9s
aws-stop
update-check
5s
update-check
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
aws-start
Error creating AWS EC2 instance with aws_cuda-10197381475-1 label
aws-start
VcpuLimitExceeded: You have requested more vCPU capacity than your current vCPU limit of 64 allows for the instance bucket that the specified instance type belongs to. Please visit http://aws.amazon.com/contact-us/ec2-request to request an adjustment to this limit.
aws-start
You have requested more vCPU capacity than your current vCPU limit of 64 allows for the instance bucket that the specified instance type belongs to. Please visit http://aws.amazon.com/contact-us/ec2-request to request an adjustment to this limit.
update-check
Unhandled error: HttpError: Validation Failed: {"resource":"Status","code":"custom","field":"state","message":"state is not included in the list"}
aws-start
The following actions uses Node.js version which is deprecated and will be forced to run on node20: ./devops/actions/aws-ec2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
aws-start
Error creating AWS EC2 on-demand instance of g5.2xlarge type with aws_cuda-10197381475-1 label
aws-start
Error creating AWS EC2 on-demand instance of g5.4xlarge type with aws_cuda-10197381475-1 label
aws-stop
The following actions uses Node.js version which is deprecated and will be forced to run on node20: ./devops/actions/aws-ec2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/