Skip to content
tests

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

Sign in to view logs

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

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

Triggered via push August 13, 2025 20:27
@azmeukazmeuk
pushed 2ff7767
main
Status Failure
Total duration 16s
Artifacts –

tests.yaml

on: push
py unit tests
7s
py unit tests
minimum dependency versions
7s
minimum dependency versions
style
14s
style
doc
6s
doc
Matrix: downstream-tests
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 10 warnings
py3.12 unit tests
Process completed with exit code 1.
py unit tests
Process completed with exit code 1.
py3.13 unit tests
Process completed with exit code 1.
doc
Process completed with exit code 1.
py3.13 scim2-cli downstream unit tests
Process completed with exit code 1.
minimum dependency versions
Process completed with exit code 1.
py3.11 unit tests
Process completed with exit code 1.
py3.10 unit tests
Process completed with exit code 1.
py3.12 scim2-cli downstream unit tests
Process completed with exit code 1.
py3.11 scim2-cli downstream unit tests
Process completed with exit code 1.
py3.12 unit tests
Failed to restore: Cache service responded with 400
py unit tests
Failed to restore: Cache service responded with 400
py3.13 unit tests
Failed to restore: Cache service responded with 400
doc
Failed to restore: Cache service responded with 400
py3.13 scim2-cli downstream unit tests
Failed to restore: Cache service responded with 400
minimum dependency versions
Failed to restore: Cache service responded with 400
py3.11 unit tests
Failed to restore: Cache service responded with 400
py3.10 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.11 scim2-cli downstream unit tests
Failed to restore: Cache service responded with 400