Skip to content

Merge branch 'sepeth-master' #160

Merge branch 'sepeth-master'

Merge branch 'sepeth-master' #160

Triggered via push September 13, 2024 13:48
Status Failure
Total duration 12m 8s
Artifacts

ci_test.yml

on: push
Check formatting
12s
Check formatting
Matrix: Build and test
Matrix: Clippy check
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 52 warnings
Check formatting
The process '/home/runner/.cargo/bin/cargo' failed with exit code 1
first doc comment paragraph is too long: src/writers.rs#L1
error: first doc comment paragraph is too long --> src/writers.rs:1:1 | 1 | / //! Describes how to extend `flexi_logger` with additional log writers 2 | | //! (implementations of the trait [`LogWriter`]), and contains two ready-to-use log writers, 3 | | //! one for writing to files ([`FileLogWriter`]), one for writing to the syslog ([`SyslogWriter`]). 4 | | //! 5 | | //! Log writers can be used in two ways: | |_ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph
first doc comment paragraph is too long: src/writers.rs#L1
error: first doc comment paragraph is too long --> src/writers.rs:1:1 | 1 | / //! Describes how to extend `flexi_logger` with additional log writers 2 | | //! (implementations of the trait [`LogWriter`]), and contains two ready-to-use log writers, 3 | | //! one for writing to files ([`FileLogWriter`]), one for writing to the syslog ([`SyslogWriter`]). 4 | | //! 5 | | //! Log writers can be used in two ways: | |_ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph
first doc comment paragraph is too long: src/formats.rs#L451
error: first doc comment paragraph is too long --> src/formats.rs:451:1 | 451 | / /// Can be used in 452 | | /// [`Logger::adaptive_format_for_stderr`](crate::Logger::adaptive_format_for_stderr) and 453 | | /// [`Logger::adaptive_format_for_stdout`](crate::Logger::adaptive_format_for_stdout) 454 | | /// to use coloring only if the output goes to a tty. 455 | | /// 456 | | /// This is helpful if the output is sometimes piped into other programs, which usually | |_ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph
first doc comment paragraph is too long: src/formats.rs#L230
error: first doc comment paragraph is too long --> src/formats.rs:230:1 | 230 | / /// A logline-formatter that produces log lines like 231 | | /// <br> 232 | | /// ```[2016-01-13 15:25:01.640870 +01:00] T[taskreader] INFO [src/foo/bar:26] Task successfully read from conf.json``` 233 | | /// <br> 234 | | /// i.e. with timestamp, thread name and file location. 235 | | /// 236 | | /// # Errors | |_ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph
first doc comment paragraph is too long: src/formats.rs#L169
error: first doc comment paragraph is too long --> src/formats.rs:169:1 | 169 | / /// A logline-formatter that produces log lines like 170 | | /// <br> 171 | | /// ```[2016-01-13 15:25:01.640870 +01:00] INFO [foo::bar] src/foo/bar.rs:26: Task successfully read from conf.json``` 172 | | /// <br> 173 | | /// i.e. with timestamp, module path and file location. 174 | | /// 175 | | /// # Errors | |_ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph
first doc comment paragraph is too long: src/formats.rs#L80
error: first doc comment paragraph is too long --> src/formats.rs:80:1 | 80 | / /// A colored version of the logline-formatter `default_format` 81 | | /// that produces log lines like <br> 82 | | /// <code><span style="color:red">ERROR</span> &#91;`my_prog::some_submodule`&#93; <span 83 | | /// style="color:red">File not found</span></code> 84 | | /// 85 | | /// See method `[style](crate::style)` if you want to influence coloring. | |_ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph
first doc comment paragraph is too long: src/formats.rs#L53
error: first doc comment paragraph is too long --> src/formats.rs:53:1 | 53 | / /// A logline-formatter that produces log lines like <br> 54 | | /// ```INFO [my_prog::some_submodule] Task successfully read from conf.json```, 55 | | /// or 56 | | /// ```INFO [my_prog::some_submodule] {a=17, b="foo"} Task successfully read from conf.json``` 57 | | /// if the kv-feature is used. 58 | | /// 59 | | /// # Errors | |_ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph note: the lint level is defined here --> src/lib.rs:4:9 | 4 | #![deny(clippy::all)] | ^^^^^^^^^^^ = note: `#[deny(clippy::too_long_first_doc_paragraph)]` implied by `#[deny(clippy::all)]`
first doc comment paragraph is too long: src/formats.rs#L451
error: first doc comment paragraph is too long --> src/formats.rs:451:1 | 451 | / /// Can be used in 452 | | /// [`Logger::adaptive_format_for_stderr`](crate::Logger::adaptive_format_for_stderr) and 453 | | /// [`Logger::adaptive_format_for_stdout`](crate::Logger::adaptive_format_for_stdout) 454 | | /// to use coloring only if the output goes to a tty. 455 | | /// 456 | | /// This is helpful if the output is sometimes piped into other programs, which usually | |_ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph
first doc comment paragraph is too long: src/formats.rs#L230
error: first doc comment paragraph is too long --> src/formats.rs:230:1 | 230 | / /// A logline-formatter that produces log lines like 231 | | /// <br> 232 | | /// ```[2016-01-13 15:25:01.640870 +01:00] T[taskreader] INFO [src/foo/bar:26] Task successfully read from conf.json``` 233 | | /// <br> 234 | | /// i.e. with timestamp, thread name and file location. 235 | | /// 236 | | /// # Errors | |_ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph
first doc comment paragraph is too long: src/formats.rs#L169
error: first doc comment paragraph is too long --> src/formats.rs:169:1 | 169 | / /// A logline-formatter that produces log lines like 170 | | /// <br> 171 | | /// ```[2016-01-13 15:25:01.640870 +01:00] INFO [foo::bar] src/foo/bar.rs:26: Task successfully read from conf.json``` 172 | | /// <br> 173 | | /// i.e. with timestamp, module path and file location. 174 | | /// 175 | | /// # Errors | |_ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph
first doc comment paragraph is too long: src/formats.rs#L80
error: first doc comment paragraph is too long --> src/formats.rs:80:1 | 80 | / /// A colored version of the logline-formatter `default_format` 81 | | /// that produces log lines like <br> 82 | | /// <code><span style="color:red">ERROR</span> &#91;`my_prog::some_submodule`&#93; <span 83 | | /// style="color:red">File not found</span></code> 84 | | /// 85 | | /// See method `[style](crate::style)` if you want to influence coloring. | |_ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph
first doc comment paragraph is too long: src/formats.rs#L53
error: first doc comment paragraph is too long --> src/formats.rs:53:1 | 53 | / /// A logline-formatter that produces log lines like <br> 54 | | /// ```INFO [my_prog::some_submodule] Task successfully read from conf.json```, 55 | | /// or 56 | | /// ```INFO [my_prog::some_submodule] {a=17, b="foo"} Task successfully read from conf.json``` 57 | | /// if the kv-feature is used. 58 | | /// 59 | | /// # Errors | |_ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_long_first_doc_paragraph note: the lint level is defined here --> src/lib.rs:4:9 | 4 | #![deny(clippy::all)] | ^^^^^^^^^^^ = note: `#[deny(clippy::too_long_first_doc_paragraph)]` implied by `#[deny(clippy::all)]`
Clippy check (ubuntu-latest)
Clippy had exited with the 101 exit code
Clippy check (macos-latest)
The job was canceled because "ubuntu-latest" failed.
Clippy check (macos-latest)
The operation was canceled.
Clippy check (windows-latest)
The job was canceled because "ubuntu-latest" failed.
Clippy check (windows-latest)
The operation was canceled.
Check formatting
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/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/
Check formatting
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@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
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
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
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
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/
Clippy check (ubuntu-latest)
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/
Clippy check (ubuntu-latest)
The following actions use a deprecated Node.js version 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/
Clippy check (ubuntu-latest)
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/
Clippy check (ubuntu-latest)
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/
Clippy check (ubuntu-latest)
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/
Clippy check (ubuntu-latest)
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/
Clippy check (macos-latest)
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/
Clippy check (macos-latest)
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/
Clippy check (macos-latest)
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/
Clippy check (macos-latest)
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/
Build and test (ubuntu-latest, stable)
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/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/
Build and test (ubuntu-latest, stable)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and test (ubuntu-latest, stable)
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/
Build and test (ubuntu-latest, stable)
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/
Build and test (ubuntu-latest, stable)
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/
Build and test (ubuntu-latest, stable)
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/
Build and test (ubuntu-latest, 1.70.0)
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/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/
Build and test (ubuntu-latest, 1.70.0)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and test (ubuntu-latest, 1.70.0)
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/
Build and test (ubuntu-latest, 1.70.0)
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/
Build and test (ubuntu-latest, 1.70.0)
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/
Build and test (ubuntu-latest, 1.70.0)
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/
Build and test (windows-latest, 1.70.0)
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/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/
Build and test (windows-latest, 1.70.0)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and test (windows-latest, 1.70.0)
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/
Build and test (windows-latest, 1.70.0)
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/
Build and test (windows-latest, 1.70.0)
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/
Build and test (windows-latest, 1.70.0)
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/
Build and test (windows-latest, stable)
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/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/
Build and test (windows-latest, stable)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and test (windows-latest, stable)
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/
Build and test (windows-latest, stable)
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/
Build and test (windows-latest, stable)
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/
Build and test (windows-latest, stable)
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/
Build and test (macos-latest, 1.70.0)
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/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/
Build and test (macos-latest, 1.70.0)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and test (macos-latest, 1.70.0)
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/
Build and test (macos-latest, 1.70.0)
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/
Build and test (macos-latest, 1.70.0)
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/
Build and test (macos-latest, 1.70.0)
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/
Build and test (macos-latest, stable)
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/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/
Build and test (macos-latest, stable)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and test (macos-latest, stable)
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/
Build and test (macos-latest, stable)
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/
Build and test (macos-latest, stable)
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/
Build and test (macos-latest, stable)
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/