Skip to content

chore: use uv-build instead of hatch as build-backend #438

chore: use uv-build instead of hatch as build-backend

chore: use uv-build instead of hatch as build-backend #438

Triggered via push August 13, 2025 20:28
Status Failure
Total duration 18s
Artifacts

tests.yaml

on: push
py unit tests
8s
py unit tests
minimum dependency versions
5s
minimum dependency versions
style
13s
style
doc
5s
doc
Matrix: downstream-tests
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 20 warnings
py3.12 scim2-client downstream unit tests
Process completed with exit code 1.
doc
Process completed with exit code 1.
py3.11 unit tests
Process completed with exit code 1.
py3.11 scim2-tester downstream unit tests
Process completed with exit code 1.
py3.12 unit tests
Process completed with exit code 1.
py3.9 unit tests
Process completed with exit code 1.
py3.10 unit tests
Process completed with exit code 1.
py3.13 scim2-tester downstream unit tests
Process completed with exit code 1.
py3.11 scim2-client downstream unit tests
Process completed with exit code 1.
py3.11 scim2-cli downstream unit tests
Process completed with exit code 1.
py3.13 unit tests
Process completed with exit code 1.
py3.12 scim2-tester downstream unit tests
Process completed with exit code 1.
py unit tests
Process completed with exit code 1.
py3.11 scim2-server downstream unit tests
Process completed with exit code 1.
py3.12 scim2-cli downstream unit tests
Process completed with exit code 1.
py3.13 scim2-cli downstream unit tests
Process completed with exit code 1.
py3.12 scim2-server downstream unit tests
Process completed with exit code 1.
minimum dependency versions
Process completed with exit code 1.
py3.13 scim2-client downstream unit tests
Process completed with exit code 1.
py3.13 scim2-server downstream unit tests
Process completed with exit code 1.
py3.12 scim2-client downstream unit tests
Failed to restore: Cache service responded with 400
doc
Failed to restore: Cache service responded with 400
py3.11 unit tests
Failed to restore: Cache service responded with 400
py3.11 scim2-tester downstream unit tests
Failed to restore: Cache service responded with 400
py3.12 unit tests
Failed to restore: Cache service responded with 400
py3.9 unit tests
Failed to restore: Cache service responded with 400
py3.10 unit tests
Failed to restore: Cache service responded with 400
py3.13 scim2-tester downstream unit tests
Failed to restore: Cache service responded with 400
py3.11 scim2-client downstream unit tests
Failed to restore: Cache service responded with 400
py3.11 scim2-cli downstream unit tests
Failed to restore: Cache service responded with 400
py3.13 unit tests
Failed to restore: Cache service responded with 400
py3.12 scim2-tester downstream unit tests
Failed to restore: Cache service responded with 400
py unit tests
Failed to restore: Cache service responded with 400
py3.11 scim2-server downstream unit tests
Failed to restore: Cache service responded with 400
py3.12 scim2-cli downstream unit tests
Failed to restore: Cache service responded with 400
py3.13 scim2-cli downstream unit tests
Failed to restore: Cache service responded with 400
py3.12 scim2-server downstream unit tests
Failed to restore: Cache service responded with 400
minimum dependency versions
Failed to restore: Cache service responded with 400
py3.13 scim2-client downstream unit tests
Failed to restore: Cache service responded with 400
py3.13 scim2-server downstream unit tests
Failed to restore: Cache service responded with 400