Update MuJoCo and MuJoCo Warp to 3.12 (#4119) #3091
push_aws_gpu.yml
on: push
run-tests
/
Start self-hosted EC2 runner
2m 20s
run-tests
/
Upload coverage to Codecov
17s
run-tests
/
Stop self-hosted EC2 runner
13s
Annotations
8 warnings
|
run-tests / Start self-hosted EC2 runner
Failed to start EC2 instance with configuration 8 in region us-west-2: We currently do not have sufficient g7e.2xlarge capacity in the Availability Zone you requested (us-west-2d). Our system will be working on provisioning additional capacity. You can currently get g7e.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-west-2a, us-west-2b, us-west-2c.
|
|
run-tests / Start self-hosted EC2 runner
Failed to start EC2 instance with configuration 7 in region us-west-2: We currently do not have sufficient g7e.2xlarge capacity in the Availability Zone you requested (us-west-2c). Our system will be working on provisioning additional capacity. You can currently get g7e.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-west-2a, us-west-2b, us-west-2d.
|
|
run-tests / Start self-hosted EC2 runner
Failed to start EC2 instance with configuration 6 in region us-west-2: We currently do not have sufficient g7e.2xlarge capacity in the Availability Zone you requested (us-west-2a). Our system will be working on provisioning additional capacity. You can currently get g7e.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-west-2b, us-west-2c, us-west-2d.
|
|
run-tests / Start self-hosted EC2 runner
Failed to start EC2 instance with configuration 5 in region us-west-2: We currently do not have sufficient g7e.2xlarge capacity in the Availability Zone you requested (us-west-2b). Our system will be working on provisioning additional capacity. You can currently get g7e.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-west-2a, us-west-2c, us-west-2d.
|
|
run-tests / Start self-hosted EC2 runner
Failed to start EC2 instance with configuration 4 in region us-east-2: We currently do not have sufficient g7e.2xlarge capacity in the Availability Zone you requested (us-east-2b). Our system will be working on provisioning additional capacity. You can currently get g7e.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2a.
|
|
run-tests / Start self-hosted EC2 runner
Failed to start EC2 instance with configuration 3 in region us-east-2: We currently do not have sufficient g7e.2xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get g7e.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b.
|
|
run-tests / Start self-hosted EC2 runner
Failed to start EC2 instance with configuration 2 in region us-east-1: We currently do not have sufficient g7e.2xlarge capacity in the Availability Zone you requested (us-east-1c). Our system will be working on provisioning additional capacity. You can currently get g7e.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-1a.
|
|
run-tests / Start self-hosted EC2 runner
Failed to start EC2 instance with configuration 1 in region us-east-1: We currently do not have sufficient g7e.2xlarge capacity in the Availability Zone you requested (us-east-1a). Our system will be working on provisioning additional capacity. You can currently get g7e.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-1c.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
coverage-gpu
Expired
|
201 KB |
sha256:afc8408b70369ac5ac14e798ca1b4c8874e50cbadfbf68037d0afecbae32cb52
|
|