Skip to content
Pull request checks

fix: use proper dependency resolution in CI #3055

Sign in to view logs

fix: use proper dependency resolution in CI

fix: use proper dependency resolution in CI #3055

Triggered via pull request October 23, 2025 04:51
@felixweinbergerfelixweinberger
synchronize #1507
fweinberger/fix-pipeline
Status Success
Total duration 1m 48s
Artifacts –

pull-request-checks.yml

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

Annotations

16 warnings
checks / Test (3.11) (ubuntu-latest) (highest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0crT5aAAAAAAxz0sICCIHQ4E1UiKb9l0CUEhMMzBFREdFMDIyMgBFZGdl
checks / Test (3.11) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.12) (ubuntu-latest) (highest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0cbT5aAAAAACREmvJgEVVQIOS/L1yWp+SUEFPRURHRTA1MTQARWRnZQ==
checks / Test (3.12) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.10) (ubuntu-latest) (highest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0crT5aAAAAACFYv3rXbaqSIdcBDZu9uz7Q0hJMzBFREdFMDQxNwBFZGdl
checks / Test (3.10) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.13) (ubuntu-latest) (highest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0crT5aAAAAADB9SZAWrdLRZYnWDaqEiolUEFPRURHRTA2MjAARWRnZQ==
checks / Test (3.13) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.13) (windows-latest) (highest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0mbT5aAAAAAADq9fSFHq7RqqLpco41Y2xUEhMMzBFREdFMDQyMABFZGdl
checks / Test (3.10) (windows-latest) (highest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0mLT5aAAAAACGiPEPeOwxRKTVUdfVUDGhREVOMzAxMDAwMTAyMDM5AEVkZ2U=
checks / Test (3.13) (windows-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.12) (windows-latest) (highest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0nbT5aAAAAADGiOfvaGhLRKsnG4OKObDxUEhMMzBFREdFMDIwNgBFZGdl
checks / Test (3.12) (windows-latest) (highest)
Failed to restore: Cache service responded with 400
checks / Test (3.11) (windows-latest) (highest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0obT5aAAAAAAd/tJNqfD/SoV7LBlYthv0Q0hJMzBFREdFMDExMQBFZGdl
checks / Test (3.11) (windows-latest) (highest)
Failed to restore: Cache service responded with 400