Skip to content

Allow the specficiation of a logging prefix when setting up a logger #162

Allow the specficiation of a logging prefix when setting up a logger

Allow the specficiation of a logging prefix when setting up a logger #162

Re-run triggered September 28, 2025 07:21
Status Failure
Total duration 3m 47s
Artifacts 1

test.yaml

on: pull_request
Build with the minimal supported versions
15s
Build with the minimal supported versions
Check formatting
17s
Check formatting
Check documentation links
15s
Check documentation links
Clippy lints
21s
Clippy lints
Coverage
59s
Coverage
Matrix: Build & test
Fit to window
Zoom out
Zoom in

Annotations

4 errors, 28 warnings, and 18 notices
Check formatting
Process completed with exit code 1.
Build & test (macos-latest, stable, 3.8)
[notice] A new release of pip is available: 21.1.1 -> 25.0.1 [notice] To update, run: python3.8 -m pip install --upgrade pip
Build & test (macos-latest, beta, 3.8)
[notice] A new release of pip is available: 21.1.1 -> 25.0.1 [notice] To update, run: python3.8 -m pip install --upgrade pip
Build & test (macos-latest, nightly, 3.8)
[notice] A new release of pip is available: 21.1.1 -> 25.0.1 [notice] To update, run: python3.8 -m pip install --upgrade pip
Build & test (ubuntu-latest, beta, 3.12)
Cache not found for keys: v0-rust-test-Linux-x64-b0ef3141-94cae5e5, v0-rust-test-Linux-x64-b0ef3141
Build & test (ubuntu-latest, beta, 3.11)
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
Build & test (ubuntu-latest, beta, 3.11)
Cache not found for keys: v0-rust-test-Linux-x64-b0ef3141-94cae5e5, v0-rust-test-Linux-x64-b0ef3141
Build & test (ubuntu-latest, nightly, 3.12)
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
Build & test (ubuntu-latest, nightly, 3.12)
Cache not found for keys: v0-rust-test-Linux-x64-69201b36-94cae5e5, v0-rust-test-Linux-x64-69201b36
Build & test (ubuntu-latest, nightly, 3.11)
Cache not found for keys: v0-rust-test-Linux-x64-69201b36-94cae5e5, v0-rust-test-Linux-x64-69201b36
Build & test (ubuntu-latest, nightly, 3.13)
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
Build & test (ubuntu-latest, nightly, 3.13)
Cache not found for keys: v0-rust-test-Linux-x64-69201b36-94cae5e5, v0-rust-test-Linux-x64-69201b36
Build & test (ubuntu-latest, beta, 3.10)
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
Build & test (ubuntu-latest, beta, 3.10)
Cache not found for keys: v0-rust-test-Linux-x64-b0ef3141-94cae5e5, v0-rust-test-Linux-x64-b0ef3141
Build & test (ubuntu-latest, nightly, 3.10)
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
Build & test (ubuntu-latest, nightly, 3.10)
Cache not found for keys: v0-rust-test-Linux-x64-69201b36-94cae5e5, v0-rust-test-Linux-x64-69201b36
Build & test (ubuntu-latest, beta, 3.13)
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
Build & test (ubuntu-latest, beta, 3.13)
Cache not found for keys: v0-rust-test-Linux-x64-b0ef3141-94cae5e5, v0-rust-test-Linux-x64-b0ef3141
Build & test (macos-latest, beta, 3.12)
Cache not found for keys: v0-rust-test-Darwin-arm64-02b83718-94cae5e5, v0-rust-test-Darwin-arm64-02b83718
Build & test (macos-latest, nightly, 3.9)
Cache not found for keys: v0-rust-test-Darwin-arm64-a5743ed5-94cae5e5, v0-rust-test-Darwin-arm64-a5743ed5
Build & test (macos-latest, nightly, 3.10)
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
Build & test (macos-latest, nightly, 3.10)
Cache not found for keys: v0-rust-test-Darwin-arm64-a5743ed5-94cae5e5, v0-rust-test-Darwin-arm64-a5743ed5
Build & test (windows-latest, nightly, 3.10)
Cache not found for keys: v0-rust-test-Windows_NT-x64-f0517e1e-94cae5e5, v0-rust-test-Windows_NT-x64-f0517e1e
Build & test (windows-latest, nightly, 3.11)
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
Build & test (windows-latest, nightly, 3.11)
Cache not found for keys: v0-rust-test-Windows_NT-x64-f0517e1e-94cae5e5, v0-rust-test-Windows_NT-x64-f0517e1e
Build & test (windows-latest, beta, 3.9)
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
Build & test (windows-latest, beta, 3.9)
Cache not found for keys: v0-rust-test-Windows_NT-x64-027c6479-94cae5e5, v0-rust-test-Windows_NT-x64-027c6479
Build & test (windows-latest, beta, 3.13)
Cache not found for keys: v0-rust-test-Windows_NT-x64-027c6479-94cae5e5, v0-rust-test-Windows_NT-x64-027c6479
Build & test (windows-latest, beta, 3.12)
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
Build & test (windows-latest, beta, 3.12)
Cache not found for keys: v0-rust-test-Windows_NT-x64-027c6479-94cae5e5, v0-rust-test-Windows_NT-x64-027c6479
Build & test (windows-latest, beta, 3.11)
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
Build & test (windows-latest, beta, 3.11)
Cache not found for keys: v0-rust-test-Windows_NT-x64-027c6479-94cae5e5, v0-rust-test-Windows_NT-x64-027c6479
Build & test (windows-latest, nightly, 3.10)
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
Build & test (windows-latest, stable, 3.10)
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
Build & test (windows-latest, nightly, 3.11)
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
Build & test (windows-latest, beta, 3.9)
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
Build & test (windows-latest, beta, 3.13)
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
Build & test (windows-latest, stable, 3.13)
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
Build & test (windows-latest, stable, 3.9)
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
Build & test (windows-latest, beta, 3.12)
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
Build & test (windows-latest, beta, 3.11)
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
Build & test (windows-latest, stable, 3.12)
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
Build & test (windows-latest, stable, 3.11)
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
Build & test (windows-latest, nightly, 3.9)
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
Build & test (windows-latest, stable, 3.8)
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
Build & test (windows-latest, beta, 3.10)
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
Build & test (windows-latest, nightly, 3.12)
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
Build & test (windows-latest, beta, 3.8)
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
Build & test (windows-latest, nightly, 3.8)
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
Build & test (windows-latest, nightly, 3.13)
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

Artifacts

Produced during runtime
Name Size Digest
code-coverage-report Expired
912 Bytes
sha256:e7889734db02dce5e5463d9362162ed01f50bca28e1e965b0cf95dcafc35d9b9