Skip to content

Separate crypto3 step #448

Separate crypto3 step

Separate crypto3 step #448

Triggered via pull request October 18, 2024 12:08
Status Failure
Total duration 1h 7m 51s
Artifacts 2

pull-request.yml

on: pull_request
Check Proof Producer  /  Prepare targets strings
0s
Check Proof Producer / Prepare targets strings
Check Proof Producer  /  Get zkLLVM run to use artifacts from
4s
Check Proof Producer / Get zkLLVM run to use artifacts from
Verify Circuit Proof  /  Produce and verify proofs
3m 35s
Verify Circuit Proof / Produce and verify proofs
Linux Crypto3 Testing with gcc  /  Build and test Linux with gcc
54m 47s
Linux Crypto3 Testing with gcc / Build and test Linux with gcc
Linux Crypto3 Testing with clang  /  Build and test Linux with clang
1h 1m
Linux Crypto3 Testing with clang / Build and test Linux with clang
Check Proof Producer  /  Build prover, generate proofs for circuits
6m 11s
Check Proof Producer / Build prover, generate proofs for circuits
Verify Circuit Proof  /  ...  /  verify-proofs
1m 7s
Verify Circuit Proof / Verify proofs / verify-proofs
Check Proof Producer  /  ...  /  run-tests
1m 42s
Check Proof Producer / Verify proof-producer proofs with EVM-placeholder / run-tests
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
Linux Crypto3 Testing with gcc / Build and test Linux with gcc
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Linux Crypto3 Testing with gcc / Build and test Linux with gcc
Process completed with exit code 137.
Linux Crypto3 Testing with gcc / Build and test Linux with gcc
The operation was canceled.
Linux Crypto3 Testing with clang / Build and test Linux with clang
The self-hosted runner: nil-githhub-actions_i-01907ae6fdb2f9101 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Check Proof Producer / Build prover, generate proofs for circuits
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Check Proof Producer / Verify proof-producer proofs with EVM-placeholder / run-tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Linux Crypto3 Testing with gcc / Build and test Linux with gcc
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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: "transpiler-output-merged-proofs". 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
proofs Expired
492 KB
transpiler-output-merged-proofs Expired
2.12 MB