Add FRI layer 0 (WIP) #7679
Triggered via pull request
November 21, 2024 18:02
andrewmilson
Status
Failure
Total duration
1d 10h 17m 53s
Billable time
6h 1m
Artifacts
–
ci.yaml
on: pull_request
Matrix: run-avx-tests
format
18s
clippy
20s
run-wasm32-wasi-tests
23s
run-neon-tests
6h 0m
run-tests
44m 54s
run-slow-tests
31m 50s
machete
1m 3s
doc
44s
run-wasm32-unknown-tests
20s
run-avx512-bench
0s
all-tests
0s
Annotations
11 errors and 1 warning
|
run-wasm32-unknown-tests
Process completed with exit code 1.
|
|
run-wasm32-wasi-tests
Process completed with exit code 101.
|
|
doc
Process completed with exit code 101.
|
|
run-slow-tests
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
run-slow-tests
The operation was canceled.
|
|
run-tests
The hosted runner: GitHub Actions 2 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
run-neon-tests
The job running on runner GitHub Actions 12 has exceeded the maximum execution time of 360 minutes.
|
|
run-neon-tests
The operation was canceled.
|
|
run-avx512-bench
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
run-avx-tests (avx2)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
run-avx-tests (avx512f)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
run-wasm32-unknown-tests
The following actions use a deprecated Node.js version and will be forced to run on node20: jetli/wasm-pack-action@v0.4.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|