Skip to content
Rust

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

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 #3290

Triggered via pull request October 4, 2024 11:57
@muzarskimuzarski
opened #1083
muzarski:internal-error-matches-no-wildcard
Status Success
Total duration 11m 8s
Artifacts –

rust.yml

on: pull_request
build
10m 58s
build
min_rust
2m 10s
min_rust
cargo_docs
43s
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/