Skip to content

refactor: Use a Rust-based filesystem storage implementation #451

refactor: Use a Rust-based filesystem storage implementation

refactor: Use a Rust-based filesystem storage implementation #451

Triggered via pull request April 9, 2026 11:26
Status Failure
Total duration 6h 5m 4s
Artifacts

on_pull_request.yaml

on: pull_request
PR title check
5s
PR title check
Doc checks  /  ...  /  Docs check
1m 53s
Doc checks / Doc checks / Docs check
Code checks  /  Actions lint check
34s
Code checks / Actions lint check
Code checks  /  Spell check
8s
Code checks / Spell check
Matrix: Code checks / Lint check / Lint check
Matrix: Code checks / Type check / Type check
Matrix: Tests / Unit tests / Unit tests
Fit to window
Zoom out
Zoom in

Annotations

37 errors
Code checks / Type check / Type check (3.11)
Process completed with exit code 1.
Code checks / Type check / Type check (3.13)
The strategy configuration was canceled because "code_checks.type_check.type_check._3_11" failed
Code checks / Type check / Type check (3.13)
The operation was canceled.
Code checks / Type check / Type check (3.14)
The strategy configuration was canceled because "code_checks.type_check.type_check._3_11" failed
Code checks / Type check / Type check (3.14)
The operation was canceled.
Code checks / Type check / Type check (3.12)
The strategy configuration was canceled because "code_checks.type_check.type_check._3_11" failed
Code checks / Type check / Type check (3.12)
The operation was canceled.
Code checks / Type check / Type check (3.10)
The strategy configuration was canceled because "code_checks.type_check.type_check._3_11" failed
Code checks / Type check / Type check (3.10)
The operation was canceled.
Tests / Unit tests / Unit tests (ubuntu-latest, 3.14)
Process completed with exit code 1.
Tests / Unit tests / Unit tests (ubuntu-latest, 3.12)
Process completed with exit code 1.
Tests / Unit tests / Unit tests (macos-latest, 3.12)
Process completed with exit code 1.
Tests / Unit tests / Unit tests (macos-latest, 3.13)
Process completed with exit code 1.
Tests / Unit tests / Unit tests (macos-latest, 3.11)
Process completed with exit code 1.
Tests / Unit tests / Unit tests (windows-latest, 3.13)
Process completed with exit code 1.
Tests / Unit tests / Unit tests (windows-latest, 3.11)
Process completed with exit code 1.
Tests / Unit tests / Unit tests (macos-latest, 3.14)
Process completed with exit code 1.
Tests / Unit tests / Unit tests (windows-latest, 3.12)
Process completed with exit code 1.
Tests / Unit tests / Unit tests (macos-latest, 3.10)
Process completed with exit code 1.
Tests / Unit tests / Unit tests (windows-latest, 3.14)
Process completed with exit code 1.
Tests / Unit tests / Unit tests (windows-latest, 3.10)
Process completed with exit code 1.
Tests / Unit tests / Unit tests (ubuntu-latest, 3.11)
The job has exceeded the maximum execution time of 6h0m0s
Tests / Unit tests / Unit tests (ubuntu-latest, 3.11)
The operation was canceled.
Tests / Unit tests / Unit tests (ubuntu-latest, 3.13)
The job has exceeded the maximum execution time of 6h0m0s
Tests / Unit tests / Unit tests (ubuntu-latest, 3.10)
The job has exceeded the maximum execution time of 6h0m0s