Skip to content

chore: add typos

chore: add typos #2668

Triggered via pull request August 15, 2025 09:48
@DaniPopesDaniPopes
synchronize #991
dani/typos3
Status Cancelled
Total duration 3m 18s
Artifacts

ci.yml

on: pull_request
Matrix: feature-checks
Matrix: miri
Matrix: test
ci success
2s
ci success
Fit to window
Zoom out
Zoom in

Annotations

26 errors, 25 warnings, and 8 notices
test ubuntu-latest stable --no-default-features
Process completed with exit code 101.
test ubuntu-latest stable
Process completed with exit code 101.
test ubuntu-latest nightly --no-default-features
Process completed with exit code 101.
test ubuntu-latest nightly
Process completed with exit code 101.
test ubuntu-latest nightly --all-features
Process completed with exit code 101.
test windows-latest stable
Process completed with exit code 1.
test windows-latest stable --no-default-features
Process completed with exit code 1.
test windows-latest nightly --no-default-features
Process completed with exit code 1.
test windows-latest nightly
Process completed with exit code 1.
test windows-latest nightly
Canceling since a higher priority waiting request for CI-dani/typos3 exists
features nightly
The operation was canceled.
features nightly
Canceling since a higher priority waiting request for CI-dani/typos3 exists
miri --no-default-features
The operation was canceled.
miri --no-default-features
Canceling since a higher priority waiting request for CI-dani/typos3 exists
miri --all-features
The operation was canceled.
miri --all-features
Canceling since a higher priority waiting request for CI-dani/typos3 exists
miri
The operation was canceled.
miri
Canceling since a higher priority waiting request for CI-dani/typos3 exists
features nightly --all-targets
The operation was canceled.
features nightly --all-targets
Canceling since a higher priority waiting request for CI-dani/typos3 exists
test windows-latest nightly --all-features
The operation was canceled.
test windows-latest nightly --all-features
Canceling since a higher priority waiting request for CI-dani/typos3 exists
features stable --all-targets
The operation was canceled.
features stable --all-targets
Canceling since a higher priority waiting request for CI-dani/typos3 exists
ci success
Process completed with exit code 1.
CI
Canceling since a higher priority waiting request for CI-dani/typos3 exists
test ubuntu-latest 1.85
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test ubuntu-latest 1.85 --features json
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test ubuntu-latest stable --no-default-features
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
docs
Cache not found for keys: v0-rust-docs-Linux-x64-d4cbedac-aed1a79a, v0-rust-docs-Linux-x64-d4cbedac
test ubuntu-latest nightly --no-default-features
Cache not found for keys: v0-rust-test-Linux-x64-d4cbedac-aed1a79a, v0-rust-test-Linux-x64-d4cbedac
test ubuntu-latest nightly
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test ubuntu-latest nightly
Cache not found for keys: v0-rust-test-Linux-x64-d4cbedac-aed1a79a, v0-rust-test-Linux-x64-d4cbedac
clippy
Cache not found for keys: v0-rust-clippy-Linux-x64-d4cbedac-aed1a79a, v0-rust-clippy-Linux-x64-d4cbedac
test ubuntu-latest nightly --all-features
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test ubuntu-latest nightly --all-features
Cache not found for keys: v0-rust-test-Linux-x64-d4cbedac-aed1a79a, v0-rust-test-Linux-x64-d4cbedac
test windows-latest 1.85 --no-default-features
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test windows-latest 1.85
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test windows-latest stable --no-default-features
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test windows-latest nightly --no-default-features
Cache not found for keys: v0-rust-test-Windows_NT-x64-64fb71d4-aed1a79a, v0-rust-test-Windows_NT-x64-64fb71d4
test windows-latest nightly
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test windows-latest nightly
Cache not found for keys: v0-rust-test-Windows_NT-x64-64fb71d4-aed1a79a, v0-rust-test-Windows_NT-x64-64fb71d4
features nightly
Cache not found for keys: v0-rust-feature-checks-Linux-x64-d4cbedac-aed1a79a, v0-rust-feature-checks-Linux-x64-d4cbedac
miri --no-default-features
Cache not found for keys: v0-rust-miri-Linux-x64-d4cbedac-aed1a79a, v0-rust-miri-Linux-x64-d4cbedac
miri --all-features
Cache not found for keys: v0-rust-miri-Linux-x64-d4cbedac-aed1a79a, v0-rust-miri-Linux-x64-d4cbedac
miri
Cache not found for keys: v0-rust-miri-Linux-x64-d4cbedac-aed1a79a, v0-rust-miri-Linux-x64-d4cbedac
features nightly --all-targets
Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 1
features nightly --all-targets
Cache not found for keys: v0-rust-feature-checks-Linux-x64-d4cbedac-aed1a79a, v0-rust-feature-checks-Linux-x64-d4cbedac
test windows-latest nightly --all-features
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test windows-latest nightly --all-features
Cache not found for keys: v0-rust-test-Windows_NT-x64-64fb71d4-aed1a79a, v0-rust-test-Windows_NT-x64-64fb71d4
features stable --all-targets
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test windows-latest 1.85 --features json
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
test windows-latest 1.85 --no-default-features
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
test windows-latest stable
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
test windows-latest 1.85
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
test windows-latest stable --no-default-features
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
test windows-latest nightly --no-default-features
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
test windows-latest nightly
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
test windows-latest nightly --all-features
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677