Skip to content
CI

Feat(primitive): moved some alloc:string to arrayvec::arrayString #2715

Sign in to view logs

Feat(primitive): moved some alloc:string to arrayvec::arrayString

Feat(primitive): moved some alloc:string to arrayvec::arrayString #2715

Re-run triggered September 19, 2025 19:07
@DaniPopesDaniPopes
#1013
SWASTIC-7:stringfix
Status Success
Total duration 6m 31s
Artifacts –

ci.yml

on: pull_request
Matrix: feature-checks
Matrix: miri
Matrix: test
wasm
37s
wasm
check no_std
43s
check no_std
typos
4s
typos
clippy
52s
clippy
docs
49s
docs
fmt
17s
fmt
deny  /  cargo deny check
18s
deny / cargo deny check
ci success
3s
ci success
Fit to window
Zoom out
Zoom in

Annotations

14 warnings and 8 notices
test ubuntu-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 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 nightly --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 ubuntu-latest stable
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
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 --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 --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 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 stable
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
features nightly --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
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 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
miri --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
miri --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 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 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 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 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 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
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 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