Skip to content

feat: deploy faucet #30627

feat: deploy faucet

feat: deploy faucet #30627

Re-run triggered December 11, 2024 19:56
Status Failure
Total duration 16m 20s
Artifacts 2

ci.yml

on: pull_request
configure
9s
configure
setup  /  start-builder
7m 1s
setup / start-builder
rough-rhino-installer
54s
rough-rhino-installer
build-images
2s
build-images
noir-build-acir-tests
0s
noir-build-acir-tests
bb-native-tests
0s
bb-native-tests
noir-format
0s
noir-format
noir-test
0s
noir-test
l1-contracts-test
0s
l1-contracts-test
Matrix: bench-e2e
Matrix: e2e
Matrix: kind-network-test
Matrix: network-test
bb-gcc
0s
bb-gcc
bb-js-test
0s
bb-js-test
noir-examples
0s
noir-examples
noir-packages-test
0s
noir-packages-test
noir-projects
0s
noir-projects
avm-format
0s
avm-format
yarn-project-formatting
3m 54s
yarn-project-formatting
yarn-project-test
7m 23s
yarn-project-test
prover-client-test
27m 16s
prover-client-test
kind-smoke-test
14m 29s
kind-smoke-test
docs-preview
7m 30s
docs-preview
bb-bench
0s
bb-bench
protocol-circuits-gates-report
4m 44s
protocol-circuits-gates-report
public-functions-size-report
1m 44s
public-functions-size-report
bb-acir-tests-bb
0s
bb-acir-tests-bb
bb-acir-tests-bb-ultra-plonk
0s
bb-acir-tests-bb-ultra-plonk
bb-acir-tests-bb-ultra-honk
0s
bb-acir-tests-bb-ultra-honk
bb-acir-tests-bb-client-ivc
0s
bb-acir-tests-bb-client-ivc
bb-acir-tests-sol
0s
bb-acir-tests-sol
bb-acir-tests-sol-honk
0s
bb-acir-tests-sol-honk
bb-acir-tests-bb-js
0s
bb-acir-tests-bb-js
Matrix: boxes-test
bench-summary
0s
bench-summary
merge-check
2s
merge-check
rerun-check
0s
rerun-check
notify
0s
notify
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 7 warnings
Error
connection error: desc = "error reading server preface: command [docker exec -i earthly-buildkitd buildctl dial-stdio] has exited with exit status 1, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=error: dial unix /run/buildkit/buildkitd.sock: connect: no such file or directory\n"
e2e (e2e_deploy_contract)
Process completed with exit code 1.
merge-check
Process completed with exit code 1.
setup / start-builder
[ { "LaunchTemplateAndOverrides": { "LaunchTemplateSpecification": { "LaunchTemplateId": "lt-019c2269d11b5c20b", "Version": "1" }, "Overrides": { "InstanceType": "m6i.32xlarge", "SubnetId": "subnet-4cfabd25", "AvailabilityZone": "us-east-2a" } }, "Lifecycle": "spot", "ErrorCode": "InsufficientInstanceCapacity", "ErrorMessage": "We currently do not have sufficient m6i.32xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6i.32xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c." } ]
setup / start-builder
[ { "LaunchTemplateAndOverrides": { "LaunchTemplateSpecification": { "LaunchTemplateId": "lt-019c2269d11b5c20b", "Version": "1" }, "Overrides": { "InstanceType": "m6i.32xlarge", "SubnetId": "subnet-4cfabd25", "AvailabilityZone": "us-east-2a" } }, "Lifecycle": "spot", "ErrorCode": "InsufficientInstanceCapacity", "ErrorMessage": "We currently do not have sufficient m6i.32xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6i.32xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c." } ]
setup / start-builder
[ { "LaunchTemplateAndOverrides": { "LaunchTemplateSpecification": { "LaunchTemplateId": "lt-019c2269d11b5c20b", "Version": "1" }, "Overrides": { "InstanceType": "m6i.32xlarge", "SubnetId": "subnet-4cfabd25", "AvailabilityZone": "us-east-2a" } }, "Lifecycle": "spot", "ErrorCode": "InsufficientInstanceCapacity", "ErrorMessage": "We currently do not have sufficient m6i.32xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6i.32xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c." } ]
setup / start-builder
[ { "LaunchTemplateAndOverrides": { "LaunchTemplateSpecification": { "LaunchTemplateId": "lt-019c2269d11b5c20b", "Version": "1" }, "Overrides": { "InstanceType": "m6i.32xlarge", "SubnetId": "subnet-4cfabd25", "AvailabilityZone": "us-east-2a" } }, "Lifecycle": "spot", "ErrorCode": "InsufficientInstanceCapacity", "ErrorMessage": "We currently do not have sufficient m6i.32xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6i.32xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c." } ]
setup / start-builder
[ { "LaunchTemplateAndOverrides": { "LaunchTemplateSpecification": { "LaunchTemplateId": "lt-019c2269d11b5c20b", "Version": "1" }, "Overrides": { "InstanceType": "m6i.32xlarge", "SubnetId": "subnet-4cfabd25", "AvailabilityZone": "us-east-2a" } }, "Lifecycle": "spot", "ErrorCode": "InsufficientInstanceCapacity", "ErrorMessage": "We currently do not have sufficient m6i.32xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6i.32xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c." } ]
setup / start-builder
[ { "LaunchTemplateAndOverrides": { "LaunchTemplateSpecification": { "LaunchTemplateId": "lt-019c2269d11b5c20b", "Version": "1" }, "Overrides": { "InstanceType": "m6i.32xlarge", "SubnetId": "subnet-4cfabd25", "AvailabilityZone": "us-east-2a" } }, "Lifecycle": "spot", "ErrorCode": "InsufficientInstanceCapacity", "ErrorMessage": "We currently do not have sufficient m6i.32xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6i.32xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c." } ]
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "ag-devnet-faucet.protocol_circuits_report.json", "ag-devnet-faucet.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/

Artifacts

Produced during runtime
Name Size
ag-devnet-faucet.protocol_circuits_report.json
36.5 MB
ag-devnet-faucet.public_functions_report.json
74.1 KB