Skip to content

fix

fix #2

Triggered via push April 9, 2025 14:49
Status Failure
Total duration 2m 44s
Artifacts

test.yml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

19 errors and 10 warnings
Test with 3.10 on ubuntu-latest
Process completed with exit code 1.
Test with 3.9 on ubuntu-latest
Process completed with exit code 1.
Test with 3.9 on ubuntu-latest
The strategy configuration was canceled because "test._3_10_ubuntu-latest_dev" failed
Test with 3.13 on ubuntu-latest
The operation was canceled.
Test with 3.13 on ubuntu-latest
The strategy configuration was canceled because "test._3_10_ubuntu-latest_dev" failed
Test with 3.12 on ubuntu-latest
The operation was canceled.
Test with 3.12 on ubuntu-latest
The strategy configuration was canceled because "test._3_10_ubuntu-latest_dev" failed
Test with 3.12 on ubuntu-latest
The operation was canceled.
Test with 3.12 on ubuntu-latest
The strategy configuration was canceled because "test._3_10_ubuntu-latest_dev" failed
Test with 3.13 on ubuntu-latest
The operation was canceled.
Test with 3.13 on ubuntu-latest
The strategy configuration was canceled because "test._3_10_ubuntu-latest_dev" failed
Test with 3.10 on ubuntu-latest
The operation was canceled.
Test with 3.10 on ubuntu-latest
The strategy configuration was canceled because "test._3_10_ubuntu-latest_dev" failed
Test with 3.11 on ubuntu-latest
The operation was canceled.
Test with 3.11 on ubuntu-latest
The strategy configuration was canceled because "test._3_10_ubuntu-latest_dev" failed
Test with 3.11 on ubuntu-latest
The operation was canceled.
Test with 3.11 on ubuntu-latest
The strategy configuration was canceled because "test._3_10_ubuntu-latest_dev" failed
Test with 3.9 on ubuntu-latest
The operation was canceled.
Test with 3.9 on ubuntu-latest
The strategy configuration was canceled because "test._3_10_ubuntu-latest_dev" failed
Test with 3.10 on ubuntu-latest
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
Test with 3.9 on ubuntu-latest
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
Test with 3.13 on ubuntu-latest
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
Test with 3.12 on ubuntu-latest
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
Test with 3.12 on ubuntu-latest
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
Test with 3.13 on ubuntu-latest
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
Test with 3.10 on ubuntu-latest
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
Test with 3.11 on ubuntu-latest
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
Test with 3.11 on ubuntu-latest
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
Test with 3.9 on ubuntu-latest
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.