Move to uv as a main tool for dependency and Python management #1292
Lorak-mmkAnnotations
25 errors and 10 warnings
|
test libev (3.12)
cannot schedule new futures after shutdown
|
|
test libev (3.12)
cannot schedule new futures after shutdown
|
|
test libev (3.11)
cannot schedule new futures after shutdown
|
|
test libev (3.11)
cannot schedule new futures after shutdown
|
|
test libev (3.11)
cannot schedule new futures after shutdown
|
|
test asyncio (3.11)
cannot schedule new futures after shutdown
|
|
test asyncio (3.11)
cannot schedule new futures after shutdown
|
|
test asyncio (3.12)
cannot schedule new futures after shutdown
|
|
test asyncio (3.12)
cannot schedule new futures after shutdown
|
|
test asyncio (3.12)
cannot schedule new futures after shutdown
|
|
test asyncio (3.12)
cannot schedule new futures after shutdown
|
|
test asyncio (3.13)
cannot schedule new futures after shutdown
|
|
test libev (3.13)
cannot schedule new futures after shutdown
|
|
test libev (3.9)
cannot schedule new futures after shutdown
|
|
test asyncore (3.11)
cannot schedule new futures after shutdown
|
|
test asyncore (3.11)
cannot schedule new futures after shutdown
|
|
test asyncore (3.11)
cannot schedule new futures after shutdown
|
|
test asyncore (3.11)
cannot schedule new futures after shutdown
|
|
test asyncore (3.11)
cannot schedule new futures after shutdown
|
|
test asyncore (3.11):
cassandra/cluster.py#L4492
cannot schedule new futures after shutdown
|
|
test asyncore (3.11)
cannot schedule new futures after shutdown
|
|
test asyncio (3.9)
cannot schedule new futures after shutdown
|
|
test asyncio (3.9)
cannot schedule new futures after shutdown
|
|
test asyncore (3.9)
cannot schedule new futures after shutdown
|
|
test asyncore (3.9)
cannot schedule new futures after shutdown
|
|
test libev (3.12)
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 libev (3.11)
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 asyncio (3.11)
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 asyncio (3.12)
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 asyncio (3.13)
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 libev (3.13)
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 libev (3.9)
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 asyncore (3.11)
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 asyncio (3.9)
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 asyncore (3.9)
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.
|