feat: Make cargo bench part of CI to ensure we don’t accidentally introduce performance regressions #1053
workflow.yml
on: pull_request
Matrix: cargo-build
cargo-clippy
51s
rustfmt
25s
ShellCheck
6s
canister-build-reproducibility
9m 15s
Matrix: cargo-tests
e2e-scenario-1
5m 26s
e2e-scenario-2
5m 43s
e2e-scenario-3
4m 37s
e2e-disable-api-if-not-fully-synced-flag
4m 51s
charge-cycles-on-reject
5m 41s
upgradability
4m 40s
set_config
5m 18s
benchmark
11m 12s
watchdog_health_status
7m 5s
watchdog_get_config
5m 11s
watchdog_metrics
6m 6s
watchdog_upgradability
5m 37s
checks-pass
0s
Annotations
3 errors and 2 warnings
ShellCheck
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/
|