Make cargo bench part of CI to ensure we don’t accidentally introduce performance regressions #1046
workflow.yml
on: pull_request
Matrix: cargo-build
cargo-clippy
57s
rustfmt
21s
ShellCheck
9s
canister-build-reproducibility
9m 20s
Matrix: cargo-tests
e2e-scenario-1
4m 59s
e2e-scenario-2
5m 8s
e2e-scenario-3
5m 23s
e2e-disable-api-if-not-fully-synced-flag
5m 20s
charge-cycles-on-reject
5m 58s
upgradability
4m 49s
set_config
5m 27s
benchmark
11m 29s
watchdog_health_status
6m 7s
watchdog_get_config
5m 19s
watchdog_metrics
5m 29s
watchdog_upgradability
42s
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/
|