Skip to content

Update time crate

Update time crate #465

Triggered via pull request August 2, 2024 10:02
Status Failure
Total duration 1m 40s
Artifacts

rust-tests.yml

on: pull_request
check-formatting-linting
30s
check-formatting-linting
tests
1m 31s
tests
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 12 warnings
field `0` is never read: pkcs11/src/config/initialization.rs#L23
error: field `0` is never read --> pkcs11/src/config/initialization.rs:23:12 | 23 | NoUser(String), | ------ ^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 23 | NoUser(()), | ~~
field `0` is never read: pkcs11/src/config/initialization.rs#L21
error: field `0` is never read --> pkcs11/src/config/initialization.rs:21:12 | 21 | Config(crate::config::config_file::ConfigError), | ------ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 21 | Config(()), | ~~
field `description` is never read: pkcs11/src/config/device.rs#L29
error: field `description` is never read --> pkcs11/src/config/device.rs:29:9 | 26 | pub struct Slot { | ---- field in this struct ... 29 | pub description: Option<String>, | ^^^^^^^^^^^ | = note: `Slot` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
struct `ClusterInstance` is never constructed: pkcs11/src/config/device.rs#L21
error: struct `ClusterInstance` is never constructed --> pkcs11/src/config/device.rs:21:12 | 21 | pub struct ClusterInstance { | ^^^^^^^^^^^^^^^ | = note: `ClusterInstance` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `log_file` is never read: pkcs11/src/config/device.rs#L15
error: field `log_file` is never read --> pkcs11/src/config/device.rs:15:9 | 14 | pub struct Device { | ------ field in this struct 15 | pub log_file: Option<PathBuf>, | ^^^^^^^^ | = note: `Device` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `0` is never read: pkcs11/src/config/config_file.rs#L9
error: field `0` is never read --> pkcs11/src/config/config_file.rs:9:10 | 9 | Yaml(serde_yaml::Error), | ---- ^^^^^^^^^^^^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 9 | Yaml(()), | ~~
field `0` is never read: pkcs11/src/config/config_file.rs#L8
error: field `0` is never read --> pkcs11/src/config/config_file.rs:8:8 | 8 | Io(std::io::Error), | -- ^^^^^^^^^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 8 | Io(()), | ~~
trait `GenericDigest` is never used: pkcs11/src/backend/sign.rs#L25
error: trait `GenericDigest` is never used --> pkcs11/src/backend/sign.rs:25:11 | 25 | pub trait GenericDigest: HashMarker + FixedOutput {} | ^^^^^^^^^^^^^
struct `KeyPair` is never constructed: pkcs11/src/backend/db/object.rs#L160
error: struct `KeyPair` is never constructed --> pkcs11/src/backend/db/object.rs:160:12 | 160 | pub struct KeyPair { | ^^^^^^^ | = note: `KeyPair` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`
field `0` is never read: pkcs11/src/config/initialization.rs#L23
error: field `0` is never read --> pkcs11/src/config/initialization.rs:23:12 | 23 | NoUser(String), | ------ ^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 23 | NoUser(()), | ~~
field `0` is never read: pkcs11/src/config/initialization.rs#L21
error: field `0` is never read --> pkcs11/src/config/initialization.rs:21:12 | 21 | Config(crate::config::config_file::ConfigError), | ------ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 21 | Config(()), | ~~
field `description` is never read: pkcs11/src/config/device.rs#L29
error: field `description` is never read --> pkcs11/src/config/device.rs:29:9 | 26 | pub struct Slot { | ---- field in this struct ... 29 | pub description: Option<String>, | ^^^^^^^^^^^ | = note: `Slot` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
struct `ClusterInstance` is never constructed: pkcs11/src/config/device.rs#L21
error: struct `ClusterInstance` is never constructed --> pkcs11/src/config/device.rs:21:12 | 21 | pub struct ClusterInstance { | ^^^^^^^^^^^^^^^ | = note: `ClusterInstance` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `log_file` is never read: pkcs11/src/config/device.rs#L15
error: field `log_file` is never read --> pkcs11/src/config/device.rs:15:9 | 14 | pub struct Device { | ------ field in this struct 15 | pub log_file: Option<PathBuf>, | ^^^^^^^^ | = note: `Device` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `0` is never read: pkcs11/src/config/config_file.rs#L9
error: field `0` is never read --> pkcs11/src/config/config_file.rs:9:10 | 9 | Yaml(serde_yaml::Error), | ---- ^^^^^^^^^^^^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 9 | Yaml(()), | ~~
field `0` is never read: pkcs11/src/config/config_file.rs#L8
error: field `0` is never read --> pkcs11/src/config/config_file.rs:8:8 | 8 | Io(std::io::Error), | -- ^^^^^^^^^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 8 | Io(()), | ~~
trait `GenericDigest` is never used: pkcs11/src/backend/sign.rs#L25
error: trait `GenericDigest` is never used --> pkcs11/src/backend/sign.rs:25:11 | 25 | pub trait GenericDigest: HashMarker + FixedOutput {} | ^^^^^^^^^^^^^
struct `KeyPair` is never constructed: pkcs11/src/backend/db/object.rs#L160
error: struct `KeyPair` is never constructed --> pkcs11/src/backend/db/object.rs:160:12 | 160 | pub struct KeyPair { | ^^^^^^^ | = note: `KeyPair` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`
check-formatting-linting
Clippy had exited with the 101 exit code
tests
Process completed with exit code 101.
check-formatting-linting
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, 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/
check-formatting-linting
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check-formatting-linting
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
check-formatting-linting
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
check-formatting-linting
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
check-formatting-linting
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
tests
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
tests
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
tests
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
tests
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
tests
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/