Skip to content
Pull request checks

fix: use proper dependency resolution in CI #3034

Sign in to view logs

fix: use proper dependency resolution in CI

fix: use proper dependency resolution in CI #3034

Triggered via pull request October 22, 2025 21:23
@felixweinbergerfelixweinberger
synchronize #1507
fweinberger/fix-pipeline
Status Failure
Total duration 2m 4s
Artifacts –

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
9s
checks / pre-commit
checks  /  readme-snippets
7s
checks / readme-snippets
Matrix: checks / test
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 16 warnings
checks / Test (3.11) (ubuntu-latest) (highest)
Process completed with exit code 1.
checks / Test (3.10) (ubuntu-latest) (highest)
Process completed with exit code 1.
checks / readme-snippets
Process completed with exit code 1.
checks / Test (3.13) (ubuntu-latest) (highest)
Process completed with exit code 1.
checks / Test (3.12) (ubuntu-latest) (highest)
Process completed with exit code 1.
checks / pre-commit
Process completed with exit code 1.
checks / Test (3.10) (windows-latest) (highest)
Process completed with exit code 1.
checks / Test (3.13) (windows-latest) (highest)
Process completed with exit code 1.
checks / Test (3.12) (windows-latest) (highest)
Process completed with exit code 1.
checks / Test (3.11) (windows-latest) (highest)
Process completed with exit code 1.
checks / Test (3.12) (ubuntu-latest) (lowest-direct)
Process completed with exit code 1.
checks / Test (3.11) (ubuntu-latest) (lowest-direct)
Process completed with exit code 1.
checks / Test (3.13) (ubuntu-latest) (lowest-direct)
Process completed with exit code 1.
checks / Test (3.10) (ubuntu-latest) (lowest-direct)
Process completed with exit code 1.
checks / Test (3.12) (windows-latest) (lowest-direct)
Process completed with exit code 1.
checks / Test (3.13) (windows-latest) (lowest-direct)
Process completed with exit code 1.
checks / Test (3.10) (windows-latest) (lowest-direct)
Process completed with exit code 1.
checks / Test (3.11) (windows-latest) (lowest-direct)
Process completed with exit code 1.
checks / Test (3.11) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.10) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.13) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.12) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.10) (windows-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.13) (windows-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.12) (windows-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.11) (windows-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.12) (ubuntu-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
checks / Test (3.11) (ubuntu-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
checks / Test (3.13) (ubuntu-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
checks / Test (3.10) (ubuntu-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
checks / Test (3.12) (windows-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
checks / Test (3.13) (windows-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
checks / Test (3.10) (windows-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
checks / Test (3.11) (windows-latest) (lowest-direct)
Failed to restore: Cache service responded with 400