Dk/scylla use metadata #1
Triggered via pull request
September 4, 2025 13:43
dkropachev
Status
Failure
Total duration
35m 34s
Artifacts
–
Annotations
25 errors
|
test asyncore (3.8)
Process completed with exit code 1.
|
|
test asyncio (3.8)
Process completed with exit code 1.
|
|
test libev (3.8)
Process completed with exit code 1.
|
|
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 libev (3.11)
cannot schedule new futures after shutdown
|
|
test libev (3.13)
cannot schedule new futures after shutdown
|
|
test libev (3.13)
cannot schedule new futures after shutdown
|
|
test asyncio (3.13)
cannot schedule new futures after shutdown
|
|
test asyncio (3.13)
cannot schedule new futures after shutdown
|
|
test asyncio (3.13)
cannot schedule new futures after shutdown
|
|
test asyncio (3.13)
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 libev (3.12)
cannot schedule new futures after shutdown
|
|
test libev (3.12)
cannot schedule new futures after shutdown
|
|
test libev (3.12)
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 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
|