Skip to content
CI

Merge pull request #1082 from jayvdb/typos #1176

Sign in to view logs

Merge pull request #1082 from jayvdb/typos

Merge pull request #1082 from jayvdb/typos #1176

Triggered via push August 20, 2024 20:08
@KeruspeKeruspe
pushed 74dbd3a
main
Status Failure
Total duration 1m 44s
Artifacts –

ci.yml

on: push
Build with no-std
11s
Check tokio02 feature
13s
Checking fmt and docs
35s
Matrix: Build and test
Matrix: Check io_safety feature
Matrix: Check wasm targets
Matrix: Cross compile

Annotations

111 errors and 74 warnings
Check io_safety feature (ubuntu-latest): src/io/read/bytes.rs#L35
unexpected `cfg` condition name: `default`
Check io_safety feature (ubuntu-latest): src/io/read/chain.rs#L168
unexpected `cfg` condition name: `default`
Check io_safety feature (ubuntu-latest): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check io_safety feature (ubuntu-latest): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check io_safety feature (ubuntu-latest): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check io_safety feature (ubuntu-latest): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check io_safety feature (ubuntu-latest): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check io_safety feature (ubuntu-latest): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check io_safety feature (ubuntu-latest): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check io_safety feature (ubuntu-latest): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build with no-std: src/utils.rs#L58
trait `Context` is never used
Build with no-std: src/future/future/mod.rs#L30
trait `FutureExt` is never used
Build with no-std
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Check tokio02 feature: src/io/read/bytes.rs#L35
unexpected `cfg` condition name: `default`
Check tokio02 feature: src/io/read/chain.rs#L168
unexpected `cfg` condition name: `default`
Check tokio02 feature: src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check tokio02 feature: src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check tokio02 feature: src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check tokio02 feature: src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check tokio02 feature: src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check tokio02 feature: src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check tokio02 feature: src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check tokio02 feature: src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check io_safety feature (windows-latest)
The job was canceled because "ubuntu-latest" failed.
Check io_safety feature (windows-latest)
The operation was canceled.
Build and test (ubuntu-latest, stable): src/io/read/bytes.rs#L35
unexpected `cfg` condition name: `default`
Build and test (ubuntu-latest, stable): src/io/read/chain.rs#L168
unexpected `cfg` condition name: `default`
Build and test (ubuntu-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, beta)
The job was canceled because "ubuntu-latest_stable" failed.
Build and test (macOS-latest, beta): src/io/read/bytes.rs#L35
unexpected `cfg` condition name: `default`
Build and test (macOS-latest, beta): src/io/read/chain.rs#L168
unexpected `cfg` condition name: `default`
Build and test (macOS-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, nightly)
The job was canceled because "ubuntu-latest_stable" failed.
Build and test (ubuntu-latest, beta)
The job was canceled because "ubuntu-latest_stable" failed.
Build and test (macOS-latest, nightly): src/io/read/bytes.rs#L35
unexpected `cfg` condition name: `default`
Build and test (ubuntu-latest, beta): src/io/read/bytes.rs#L35
unexpected `cfg` condition name: `default`
Build and test (macOS-latest, nightly): src/io/read/chain.rs#L168
unexpected `cfg` condition name: `default`
Build and test (ubuntu-latest, beta): src/io/read/chain.rs#L168
unexpected `cfg` condition name: `default`
Build and test (macOS-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, beta): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (windows-latest, nightly)
The job was canceled because "ubuntu-latest_stable" failed.
Build and test (macOS-latest, stable)
The job was canceled because "ubuntu-latest_stable" failed.
Build and test (macOS-latest, stable): src/io/read/bytes.rs#L35
unexpected `cfg` condition name: `default`
Build and test (macOS-latest, stable): src/io/read/chain.rs#L168
unexpected `cfg` condition name: `default`
Build and test (macOS-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (macOS-latest, stable): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Check wasm targets (stable): src/io/read/bytes.rs#L35
unexpected `cfg` condition name: `default`
Check wasm targets (stable): src/io/read/chain.rs#L168
unexpected `cfg` condition name: `default`
Check wasm targets (stable): src/io/buf_writer.rs#L117
field `1` is never read
Check wasm targets (stable)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Build and test (ubuntu-latest, nightly)
The job was canceled because "ubuntu-latest_stable" failed.
Build and test (ubuntu-latest, nightly): src/io/read/bytes.rs#L35
unexpected `cfg` condition name: `default`
Build and test (ubuntu-latest, nightly): src/io/read/chain.rs#L168
unexpected `cfg` condition name: `default`
Build and test (ubuntu-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (ubuntu-latest, nightly): src/utils.rs#L249
unexpected `cfg` condition value: `io-safety`
Build and test (windows-latest, beta)
The job was canceled because "ubuntu-latest_stable" failed.
Build and test (windows-latest, beta)
The operation was canceled.
Build and test (windows-latest, stable)
The job was canceled because "ubuntu-latest_stable" failed.
Build and test (windows-latest, stable)
The operation was canceled.
Check wasm targets (beta)
The job was canceled because "stable" failed.
Check wasm targets (beta)
The operation was canceled.
Check wasm targets (nightly)
The job was canceled because "stable" failed.
Check wasm targets (nightly)
The operation was canceled.
Checking fmt and docs
Process completed with exit code 101.
Cross compile (powerpc-unknown-linux-gnu)
Process completed with exit code 101.
Cross compile (i686-unknown-linux-gnu)
The job was canceled because "powerpc-unknown-linux-gnu" failed.
Cross compile (i686-unknown-linux-gnu)
Process completed with exit code 101.
Cross compile (powerpc64-unknown-linux-gnu)
The job was canceled because "powerpc-unknown-linux-gnu" failed.
Cross compile (powerpc64-unknown-linux-gnu)
The operation was canceled.
Cross compile (arm-linux-androideabi)
The job was canceled because "powerpc-unknown-linux-gnu" failed.
Cross compile (arm-linux-androideabi)
The operation was canceled.
Check io_safety feature (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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 io_safety feature (ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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 with no-std
The following actions uses node12 which is deprecated and will be forced to run on node16: 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 with no-std
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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 tokio02 feature
The following actions uses node12 which is deprecated and will be forced to run on node16: 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 tokio02 feature
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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 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/
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@v3, 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 (macOS-latest, beta)
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, beta)
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, beta)
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, beta)
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, nightly)
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, beta)
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, nightly)
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, beta)
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, nightly)
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, beta)
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, nightly)
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, beta)
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/
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/
Check wasm targets (stable)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions/cache@v2, 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 wasm targets (stable)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions/cache@v2, 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 wasm targets (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/
Check wasm targets (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/
Check wasm targets (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/
Check wasm targets (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, nightly)
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, nightly)
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, nightly)
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, nightly)
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 (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/
Check wasm targets (beta)
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 wasm targets (beta)
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 wasm targets (beta)
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 wasm targets (beta)
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 wasm targets (nightly)
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 wasm targets (nightly)
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 wasm targets (nightly)
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 wasm targets (nightly)
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/
Checking fmt and docs
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/
Checking fmt and docs
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
Checking fmt and docs
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/
Checking fmt and docs
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/
Checking fmt and docs
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/
Checking fmt and docs
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/
Cross compile (powerpc-unknown-linux-gnu)
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/
Cross compile (powerpc-unknown-linux-gnu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
Cross compile (powerpc-unknown-linux-gnu)
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/
Cross compile (powerpc-unknown-linux-gnu)
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/
Cross compile (powerpc-unknown-linux-gnu)
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/
Cross compile (powerpc-unknown-linux-gnu)
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/
Cross compile (i686-unknown-linux-gnu)
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/
Cross compile (i686-unknown-linux-gnu)
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/
Cross compile (i686-unknown-linux-gnu)
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/
Cross compile (i686-unknown-linux-gnu)
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/
Cross compile (powerpc64-unknown-linux-gnu)
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/
Cross compile (powerpc64-unknown-linux-gnu)
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/
Cross compile (powerpc64-unknown-linux-gnu)
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/
Cross compile (powerpc64-unknown-linux-gnu)
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/
Cross compile (arm-linux-androideabi)
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/
Cross compile (arm-linux-androideabi)
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/
Cross compile (arm-linux-androideabi)
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/
Cross compile (arm-linux-androideabi)
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/