Make cargo bench part of CI to ensure we don’t accidentally introduce performance regressions #1031
Triggered via pull request
September 20, 2023 12:07
Status
Failure
Total duration
26m 18s
Artifacts
–
workflow.yml
on: pull_request
Matrix: cargo-build
cargo-clippy
7m 18s
rustfmt
22s
ShellCheck
9s
canister-build-reproducibility
8m 57s
Matrix: cargo-tests
e2e-scenario-1
6m 18s
e2e-scenario-2
4m 42s
e2e-scenario-3
5m 34s
e2e-disable-api-if-not-fully-synced-flag
4m 55s
charge-cycles-on-reject
5m 10s
upgradability
4m 48s
set_config
4m 29s
watchdog_health_status
5m 25s
watchdog_get_config
4m 57s
watchdog_metrics
5m 47s
watchdog_upgradability
6m 41s
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/
|