Skip to content

Bump thiserror from 1.0.37 to 1.0.49 in /native #621

Bump thiserror from 1.0.37 to 1.0.49 in /native

Bump thiserror from 1.0.37 to 1.0.49 in /native #621

Triggered via pull request October 2, 2023 02:37
Status Failure
Total duration 13m 13s
Artifacts 2
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci.yml

on: pull_request
Matrix: Rust unit tests
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

142 errors and 117 warnings
typecheck
Process completed with exit code 1.
Rust unit tests (macos-latest)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
Rust unit tests (macos-latest)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
Rust unit tests (macos-latest)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
Rust unit tests (macos-latest)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
Rust unit tests (macos-latest)
Unable to create clippy annotations! Reason: HttpError: Resource not accessible by integration
Rust unit tests (macos-latest)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
Rust unit tests (macos-latest)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
Rust unit tests (ubuntu-latest)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
Rust unit tests (ubuntu-latest)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
Rust unit tests (ubuntu-latest)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
Rust unit tests (ubuntu-latest)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
Rust unit tests (ubuntu-latest)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
Rust unit tests (ubuntu-latest)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
Rust unit tests (ubuntu-latest)
Unable to create clippy annotations! Reason: HttpError: Resource not accessible by integration
test (ubuntu-latest, 3.8)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.8)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.8)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.8)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.8)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.8)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.8)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.8)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.9)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.9)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.9)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.9)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.10)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.9)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.10)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.9)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.10)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.9)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.10)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.9)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.10)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.10)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.10)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.10)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.11)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.11)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.11)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.11)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.11)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.11)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.11)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.11)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
Rust unit tests (windows-latest)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
Rust unit tests (windows-latest)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
Rust unit tests (windows-latest)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
Rust unit tests (windows-latest)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
Rust unit tests (windows-latest)
Unable to create clippy annotations! Reason: HttpError: Resource not accessible by integration
Rust unit tests (windows-latest)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
Rust unit tests (windows-latest)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (ubuntu-latest, 3.12-dev)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.12-dev)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.12-dev)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.12-dev)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.12-dev)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.12-dev)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/target'
test (ubuntu-latest, 3.12-dev)
ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (ubuntu-latest, 3.12-dev)
Error: ENOENT: no such file or directory, opendir '/home/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.9)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.9)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.9)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.9)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.9)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.9)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.9)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.9)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (windows-latest, 3.10)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.10)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.10)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.10)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.10)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.10)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.10)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.10)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.8)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.8)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.8)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.8)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.8)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.8)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.8)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.8)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.9)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.9)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.9)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.9)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.9)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.9)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.9)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.9)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (macos-latest, 3.8)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.8)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.8)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.8)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.8)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.8)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.8)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.8)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.11)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.11)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.11)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.11)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.11)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.11)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.11)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.11)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (windows-latest, 3.12-dev)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.12-dev)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.12-dev)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.12-dev)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.12-dev)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.12-dev)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.12-dev)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.12-dev)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (macos-latest, 3.10)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.10)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.10)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.10)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.10)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.10)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.10)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.10)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.12-dev)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.12-dev)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.12-dev)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.12-dev)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.12-dev)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.12-dev)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/target'
test (macos-latest, 3.12-dev)
ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (macos-latest, 3.12-dev)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/native/target/tests/trybuild'
test (windows-latest, 3.11)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.11)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.11)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.11)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.11)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.11)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\target'
test (windows-latest, 3.11)
ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
test (windows-latest, 3.11)
Error: ENOENT: no such file or directory, opendir 'D:\a\LibCST\LibCST\native\target\tests\trybuild'
Rustfmt
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
Rustfmt
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/
Rustfmt
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/
Rustfmt
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/
Rustfmt
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/
Rust unit tests (macos-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@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/
Rust unit tests (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/
Rust unit tests (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/
Rust unit tests (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/
Rust unit tests (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/
Rust unit tests (macos-latest)
It seems that this Action is executed from the forked repository.
Rust unit tests (macos-latest)
GitHub Actions are not allowed to create Check annotations, when executed for a forked repos. See https://github.com/actions-rs/clippy-check/issues/2 for details.
Rust unit tests (macos-latest)
binary comparison to literal `Option::None`
Rust unit tests (macos-latest)
the following explicit lifetimes could be elided: 'a
Rust unit tests (macos-latest)
the following explicit lifetimes could be elided: 'a
Rust unit tests (macos-latest)
deref which would be done by auto-deref
Rust unit tests (macos-latest)
deref which would be done by auto-deref
Rust unit tests (macos-latest)
deref which would be done by auto-deref
Rust unit tests (macos-latest)
deref which would be done by auto-deref
Rust unit tests (macos-latest)
deref which would be done by auto-deref
Rust unit tests (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@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/
Rust unit tests (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/
Rust unit tests (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/
Rust unit tests (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/
Rust unit tests (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/
Rust unit tests (ubuntu-latest)
It seems that this Action is executed from the forked repository.
Rust unit tests (ubuntu-latest)
GitHub Actions are not allowed to create Check annotations, when executed for a forked repos. See https://github.com/actions-rs/clippy-check/issues/2 for details.
Rust unit tests (ubuntu-latest)
binary comparison to literal `Option::None`
Rust unit tests (ubuntu-latest)
the following explicit lifetimes could be elided: 'a
Rust unit tests (ubuntu-latest)
the following explicit lifetimes could be elided: 'a
Rust unit tests (ubuntu-latest)
deref which would be done by auto-deref
Rust unit tests (ubuntu-latest)
deref which would be done by auto-deref
Rust unit tests (ubuntu-latest)
deref which would be done by auto-deref
Rust unit tests (ubuntu-latest)
deref which would be done by auto-deref
Rust unit tests (ubuntu-latest)
deref which would be done by auto-deref
test (ubuntu-latest, 3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (ubuntu-latest, 3.8)
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/
test (ubuntu-latest, 3.8)
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/
test (ubuntu-latest, 3.8)
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/
test (ubuntu-latest, 3.8)
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/
test (ubuntu-latest, 3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (ubuntu-latest, 3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (ubuntu-latest, 3.10)
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/
test (ubuntu-latest, 3.9)
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/
test (ubuntu-latest, 3.10)
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/
test (ubuntu-latest, 3.9)
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/
test (ubuntu-latest, 3.10)
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/
test (ubuntu-latest, 3.9)
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/
test (ubuntu-latest, 3.10)
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/
test (ubuntu-latest, 3.9)
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/
test (ubuntu-latest, 3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (ubuntu-latest, 3.11)
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/
test (ubuntu-latest, 3.11)
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/
test (ubuntu-latest, 3.11)
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/
test (ubuntu-latest, 3.11)
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/
Rust unit tests (windows-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@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/
Rust unit tests (windows-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/
Rust unit tests (windows-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/
Rust unit tests (windows-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/
Rust unit tests (windows-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/
Rust unit tests (windows-latest)
It seems that this Action is executed from the forked repository.
Rust unit tests (windows-latest)
GitHub Actions are not allowed to create Check annotations, when executed for a forked repos. See https://github.com/actions-rs/clippy-check/issues/2 for details.
test (ubuntu-latest, 3.12-dev)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (ubuntu-latest, 3.12-dev)
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/
test (ubuntu-latest, 3.12-dev)
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/
test (ubuntu-latest, 3.12-dev)
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/
test (ubuntu-latest, 3.12-dev)
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/
test (macos-latest, 3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (macos-latest, 3.9)
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/
test (macos-latest, 3.9)
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/
test (macos-latest, 3.9)
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/
test (macos-latest, 3.9)
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/
test (windows-latest, 3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (windows-latest, 3.10)
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/
test (windows-latest, 3.10)
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/
test (windows-latest, 3.10)
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/
test (windows-latest, 3.10)
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/
test (windows-latest, 3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (windows-latest, 3.8)
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/
test (windows-latest, 3.8)
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/
test (windows-latest, 3.8)
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/
test (windows-latest, 3.8)
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/
test (windows-latest, 3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (windows-latest, 3.9)
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/
test (windows-latest, 3.9)
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/
test (windows-latest, 3.9)
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/
test (windows-latest, 3.9)
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/
test (macos-latest, 3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (macos-latest, 3.8)
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/
test (macos-latest, 3.8)
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/
test (macos-latest, 3.8)
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/
test (macos-latest, 3.8)
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/
test (macos-latest, 3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (macos-latest, 3.11)
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/
test (macos-latest, 3.11)
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/
test (macos-latest, 3.11)
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/
test (macos-latest, 3.11)
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/
test (windows-latest, 3.12-dev)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (windows-latest, 3.12-dev)
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/
test (windows-latest, 3.12-dev)
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/
test (windows-latest, 3.12-dev)
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/
test (windows-latest, 3.12-dev)
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/
test (macos-latest, 3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (macos-latest, 3.10)
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/
test (macos-latest, 3.10)
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/
test (macos-latest, 3.10)
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/
test (macos-latest, 3.10)
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/
test (macos-latest, 3.12-dev)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (macos-latest, 3.12-dev)
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/
test (macos-latest, 3.12-dev)
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/
test (macos-latest, 3.12-dev)
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/
test (macos-latest, 3.12-dev)
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/
test (windows-latest, 3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test (windows-latest, 3.11)
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/
test (windows-latest, 3.11)
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/
test (windows-latest, 3.11)
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/
test (windows-latest, 3.11)
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/

Artifacts

Produced during runtime
Name Size
coverage Expired
992 KB
sphinx-docs Expired
20.1 MB