Skip to content
Rust

error: use explicit matches for errors when the decision is crucial for correctness/performance #3308

Sign in to view logs

error: use explicit matches for errors when the decision is crucial for correctness/performance

error: use explicit matches for errors when the decision is crucial for correctness/performance #3308

Triggered via pull request October 14, 2024 13:51
@muzarskimuzarski
synchronize #1083
muzarski:internal-error-matches-no-wildcard
Status Success
Total duration 11m 3s
Artifacts –

rust.yml

on: pull_request
build
10m 53s
build
min_rust
2m 24s
min_rust
cargo_docs
34s
cargo_docs
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
cargo_docs
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
min_rust
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/