chore(master): Release 0.65.2 #28828
AztecBotci.yml
on: pull_request
configure
7s
bb-native-tests
11m 1s
noir-format
0s
noir-test
0s
l1-contracts-test
0s
Matrix: bench-e2e
Matrix: e2e
Matrix: kind-network-test
Matrix: network-test
bb-gcc
36s
bb-js-test
5m 1s
noir-examples
0s
noir-packages-test
4m 52s
noir-projects
0s
avm-format
0s
yarn-project-formatting
1m 18s
yarn-project-test
1m 16s
prover-client-test
4m 58s
kind-smoke-test
4m 48s
docs-preview
4m 50s
bb-bench
8m 3s
protocol-circuits-gates-report
3m 35s
public-functions-size-report
24s
bb-acir-tests-bb
4m 31s
bb-acir-tests-bb-ultra-plonk
9m 39s
bb-acir-tests-bb-ultra-honk
3m 29s
bb-acir-tests-bb-mega-honk
7m 29s
bb-acir-tests-sol
1m 56s
bb-acir-tests-sol-honk
20s
bb-acir-tests-bb-js
7m 49s
Matrix: boxes-test
bench-summary
13s
Annotations
30 errors
|
e2e (e2e_block_building)
Process completed with exit code 1.
|
|
public-functions-size-report
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
public-functions-size-report
The operation was canceled.
|
|
bench-summary
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
bench-summary
Process completed with exit code 143.
|
|
docs-preview
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
docs-preview
The operation was canceled.
|
|
kind-network-test (4epochs.test.ts, 16-validators, 16core-tester-x86, 60)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
kind-network-test (4epochs.test.ts, 16-validators, 16core-tester-x86, 60)
Process completed with exit code 143.
|
|
bb-acir-tests-bb-js
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
bb-acir-tests-bb-js
Process completed with exit code 143.
|
|
kind-smoke-test
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
bb-acir-tests-bb-mega-honk
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
bb-acir-tests-bb-mega-honk
Process completed with exit code 143.
|
|
kind-network-test (transfer.test.ts, 16-validators, 16core-tester-x86, 60)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
kind-network-test (transfer.test.ts, 16-validators, 16core-tester-x86, 60)
The operation was canceled.
|
|
kind-network-test (reorg.test.ts, 16-validators, 16core-tester-x86-high-memory, 90)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
kind-network-test (reorg.test.ts, 16-validators, 16core-tester-x86-high-memory, 90)
Process completed with exit code 143.
|
|
network-test (test-transfer.sh)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
boxes
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Error
async force execution for +build: unlazy force execution: failed to get edge: inconsistent graph state
|
|
boxes
Process completed with exit code 143.
|
|
kind-network-test (gating-passive.test.ts, 16-validators, 16core-tester-x86, 60)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
kind-network-test (gating-passive.test.ts, 16-validators, 16core-tester-x86, 60)
Process completed with exit code 143.
|
|
prover-client-test
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
prover-client-test
Process completed with exit code 143.
|
|
protocol-circuits-gates-report
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
protocol-circuits-gates-report
The operation was canceled.
|
|
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"
|
|
merge-check
Process completed with exit code 1.
|