chore: have 'aztec' honour the 'DEBUG' env var #24311
Annotations
7 warnings
|
Start EC2 runner
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-0e270d2478122da81",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6a.32xlarge",
"SubnetId": "subnet-4cfabd25",
"AvailabilityZone": "us-east-2a"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6a.32xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6a.32xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
|
Start EC2 runner
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-0e270d2478122da81",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6a.32xlarge",
"SubnetId": "subnet-4cfabd25",
"AvailabilityZone": "us-east-2a"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6a.32xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6a.32xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
|
Start EC2 runner
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-0e270d2478122da81",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6a.32xlarge",
"SubnetId": "subnet-4cfabd25",
"AvailabilityZone": "us-east-2a"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6a.32xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6a.32xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
|
Start EC2 runner
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-0e270d2478122da81",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6a.32xlarge",
"SubnetId": "subnet-4cfabd25",
"AvailabilityZone": "us-east-2a"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6a.32xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6a.32xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
|
Start EC2 runner
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-0e270d2478122da81",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6a.32xlarge",
"SubnetId": "subnet-4cfabd25",
"AvailabilityZone": "us-east-2a"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6a.32xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6a.32xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
|
Start EC2 runner
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-0e270d2478122da81",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6a.32xlarge",
"SubnetId": "subnet-4cfabd25",
"AvailabilityZone": "us-east-2a"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6a.32xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6a.32xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "ad-aztec-honour-debug.protocol_circuits_report.json", "ad-aztec-honour-debug.public_functions_report.json".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Loading