Skip to content

Use htree for inode_at, fix inode_at performance #291

Use htree for inode_at, fix inode_at performance

Use htree for inode_at, fix inode_at performance #291

Triggered via pull request May 13, 2026 07:02
@EeemsEeems
synchronize #32
htree
Status Failure
Total duration 3m 6s
Artifacts –

build.yaml

on: pull_request
Matrix: Lint codebase
Generate test ext4 image
34s
Generate test ext4 image
Matrix: Fuzz
Matrix: Test
Matrix: Build wheel
Build sdist
Build sdist
Build wheel
Build wheel
Publish to PyPi
0s
Publish to PyPi
Add release artifacts
0s
Add release artifacts
Update the AUR
0s
Update the AUR
Fit to window
Zoom out
Zoom in

Annotations

12 errors, 1 warning, and 4 notices
Test (macos-latest, 3.13)
Process completed with exit code 1.
Test (macos-latest, 3.14)
Process completed with exit code 1.
Test (ubuntu-latest, 3.11)
Process completed with exit code 1.
Test (ubuntu-latest, 3.13)
Process completed with exit code 1.
Test (ubuntu-latest, 3.14)
Process completed with exit code 1.
Test (macos-latest, 3.11)
Process completed with exit code 1.
Test (ubuntu-latest, 3.12)
Process completed with exit code 1.
Test (windows-latest, 3.13)
Process completed with exit code 1.
Test (windows-latest, 3.11)
Process completed with exit code 1.
Test (windows-latest, 3.12)
Process completed with exit code 1.
Test (windows-latest, 3.14)
Process completed with exit code 1.
Test (macos-latest, 3.12)
Process completed with exit code 1.
Test (macos-latest, 3.12)
Failed to restore: Failed to GetCacheEntryDownloadURL: Unable to make request: ETIMEDOUT If you are using self-hosted runners, please make sure your runner has access to all GitHub endpoints: https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github
Test (windows-latest, 3.13)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Test (windows-latest, 3.11)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Test (windows-latest, 3.12)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Test (windows-latest, 3.14)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026