fix: barretenberg readme scare warning #23751
ci.yml
on: pull_request
configure
9s
Matrix: e2e
bb-gcc
0s
bb-js-test
1m 12s
noir-format
0s
noir-test
0s
noir-examples
1m 30s
noir-packages-test
9m 25s
noir-projects
11m 4s
avm-format
0s
yarn-project-formatting
4m 40s
yarn-project-test
6m 47s
prover-client-test
12m 45s
network-test-fake-proofs
11m 36s
l1-contracts-test
0s
docs-preview
8m 8s
Matrix: bench-e2e
bb-bench
0s
protocol-circuits-gates-report
6m 21s
public-functions-size-report
1m 13s
bb-acir-tests-bb
8m 20s
bb-acir-tests-bb-ultra-plonk
11m 4s
bb-acir-tests-bb-ultra-honk
7m 18s
bb-acir-tests-bb-mega-honk
9m 14s
bb-acir-tests-sol
3m 32s
bb-acir-tests-sol-honk
2m 43s
bb-acir-tests-bb-js
13m 13s
Matrix: boxes-test
bench-summary
0s
rerun-check
3s
notify
0s
Annotations
4 errors and 11 warnings
Error
* command failed: docker run --privileged --env BUILDKIT_TLS_ENABLED=false --env BUILDKIT_MAX_PARALLELISM=10 --env CACHE_SIZE_PCT=50 --env BUILDKIT_DEBUG=false --env BUILDKIT_TCP_TRANSPORT_ENABLED=false --label dev.earthly.settingshash=d3f43382245f6d16 --mount type=volume,source=earthly-cache,dst=/tmp/earthly --publish 127.0.0.1:8371:8371/tcp -d --pull missing --name earthly-buildkitd docker.io/earthly/buildkitd:v0.8.10: exit status 125: docker: Error response from daemon: Conflict. The container name "/earthly-buildkitd" is already in use by container "10ea8431f2fd22573427105c75bea6de9db7f7e7f2f5810e1bd3e35a9579d4a2". You have to remove (or rename) that container to be able to reuse that name. See 'docker run --help'.: exit status 125
|
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-static-calls)
Process completed with exit code 255.
|
merge-check
Process completed with exit code 1.
|
public-functions-size-report
The following actions use a deprecated Node.js version and will be forced to run on node20: noir-lang/noir-gates-diff@d88f7523b013b9edd3f31c5cfddaef87a3fe1b48. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
e2e (e2e-max-block-number)
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-090f87b36aad01e7d",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6in.2xlarge"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6in.2xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6in.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
e2e (e2e-max-block-number)
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-090f87b36aad01e7d",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6in.2xlarge"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6in.2xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6in.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
protocol-circuits-gates-report
The following actions use a deprecated Node.js version and will be forced to run on node20: vezenovm/noir-gates-diff@acf12797860f237117e15c0d6e08d64253af52b6. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
e2e (e2e-cross-chain-messaging)
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-090f87b36aad01e7d",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6in.2xlarge"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6in.2xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6in.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
e2e (e2e-avm-simulator)
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-090f87b36aad01e7d",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6in.2xlarge"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6in.2xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6in.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
e2e (e2e-2-pxes)
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-090f87b36aad01e7d",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6in.2xlarge"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6in.2xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6in.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
e2e (e2e-2-pxes)
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-090f87b36aad01e7d",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6in.2xlarge"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6in.2xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6in.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
e2e (e2e-block-building)
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-090f87b36aad01e7d",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6in.2xlarge"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6in.2xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6in.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c."
}
]
|
e2e (e2e-lending-contract)
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-090f87b36aad01e7d",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6in.2xlarge"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6in.2xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6in.2xlarge 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: "ad-bb-scare-warning.protocol_circuits_report.json", "ad-bb-scare-warning.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 | |
---|---|---|
ad-bb-scare-warning.protocol_circuits_report.json
Expired
|
8.93 MB |
|
ad-bb-scare-warning.public_functions_report.json
Expired
|
71.5 KB |
|