Skip to content

Move optimizations from sql to vm (#484) #520

Move optimizations from sql to vm (#484)

Move optimizations from sql to vm (#484) #520

Triggered via push October 30, 2023 16:46
Status Failure
Total duration 43m 17s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

benchmarks.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
run benchmarks
Process completed with exit code 128.
run benchmarks
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
run benchmarks
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
run benchmarks
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
run benchmarks
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
run benchmarks
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/