fix: Use data dir for lmdb forks #16876
You are viewing an older attempt in the history of this workflow run.
View latest attempt.
Triggered via pull request
August 14, 2024 13:43
Status
Failure
Total duration
1h 6m 32s
Artifacts
–
ci.yml
on: pull_request
changes
14s
setup
/
start-builder
20s
bb-gcc
0s
bb-native-tests
0s
bb-js-test
0s
noir-format
0s
noir-test
0s
noir-examples
0s
noir-packages-test
0s
avm-format
0s
l1-contracts-test
0s
docs-preview
35m 6s
Matrix: e2e
yarn-project-formatting
2m 13s
yarn-project-test
5m 24s
prover-client-test
7m 51s
Matrix: bench-e2e
bb-acir-tests-bb
0s
bb-acir-tests-sol
0s
bb-acir-tests-sol-honk
0s
bb-acir-tests-bb-js
0s
Matrix: boxes-test
bench-summary
21m 6s
rerun-check
5s
notify
0s
Annotations
3 errors and 4 warnings
Error:
yarn-project/end-to-end/Earthfile#L47
The command RUN docker run -e HARDWARE_CONCURRENCY=$hardware_concurrency --rm aztecprotocol/end-to-end:$AZTEC_DOCKER_TAG $test || $allow_fail did not complete successfully. Exit code 1
|
e2e (e2e-p2p)
Process completed with exit code 1.
|
merge-check
Process completed with exit code 1.
|
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/
|
bench-summary
Unexpected input(s) 'dockerhub_password', valid inputs are ['concurrency_key']
|
bench-summary
Unexpected input(s) 'dockerhub_password', valid inputs are ['concurrency_key']
|
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: "palla-use-data-dir-for-forks.protocol_circuits_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/
|