Make cargo bench part of CI to ensure we don’t accidentally introduce performance regressions #1040
workflow.yml
on: pull_request
Matrix: cargo-build
cargo-clippy
56s
rustfmt
27s
ShellCheck
6s
canister-build-reproducibility
9m 8s
Matrix: cargo-tests
e2e-scenario-1
4m 39s
e2e-scenario-2
4m 40s
e2e-scenario-3
4m 28s
e2e-disable-api-if-not-fully-synced-flag
4m 49s
charge-cycles-on-reject
4m 40s
upgradability
4m 36s
set_config
5m 31s
benchmark
14m 41s
watchdog_health_status
5m 3s
watchdog_get_config
4m 48s
watchdog_metrics
5m 16s
watchdog_upgradability
57s
checks-pass
0s
Annotations
4 errors and 2 warnings
ShellCheck
Process completed with exit code 1.
|
watchdog_upgradability
Process completed with exit code 1.
|
e2e-scenario-1
Process completed with exit code 1.
|
benchmark
Process completed with exit code 1.
|
rustfmt
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
cargo-clippy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|