Make cargo bench part of CI to ensure we don’t accidentally introduce performance regressions #1045
workflow.yml
on: pull_request
Matrix: cargo-build
cargo-clippy
43s
rustfmt
24s
ShellCheck
6s
canister-build-reproducibility
10m 22s
Matrix: cargo-tests
e2e-scenario-1
5m 59s
e2e-scenario-2
6m 19s
e2e-scenario-3
5m 45s
e2e-disable-api-if-not-fully-synced-flag
5m 4s
charge-cycles-on-reject
6m 45s
upgradability
5m 4s
set_config
4m 33s
benchmark
11m 6s
watchdog_health_status
6m 14s
watchdog_get_config
6m 25s
watchdog_metrics
4m 59s
watchdog_upgradability
44s
checks-pass
0s
Annotations
3 errors and 2 warnings
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/
|