Make cargo bench part of CI to ensure we don’t accidentally introduce performance regressions #1032
Triggered via pull request
September 20, 2023 13:35
dragoljub-duric
Status
Failure
Total duration
18m 31s
Artifacts
–
workflow.yml
on: pull_request
Matrix: cargo-build
cargo-clippy
1m 2s
rustfmt
20s
ShellCheck
11s
canister-build-reproducibility
10m 41s
Matrix: cargo-tests
e2e-scenario-1
4m 53s
e2e-scenario-2
5m 48s
e2e-scenario-3
5m 35s
e2e-disable-api-if-not-fully-synced-flag
5m 6s
charge-cycles-on-reject
5m 1s
upgradability
4m 51s
set_config
4m 34s
watchdog_health_status
6m 55s
watchdog_get_config
5m 14s
watchdog_metrics
6m 11s
watchdog_upgradability
5m 32s
checks-pass
0s
Annotations
1 error and 2 warnings
|
e2e-scenario-1
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/
|