perf: optimize was_applied fast path for known LWT statements #49
Annotations
39 errors and 6 warnings
|
test libev (3.14)
cannot schedule new futures after shutdown
|
|
test libev (3.14)
cannot schedule new futures after shutdown
|
|
test libev (3.14)
cannot schedule new futures after shutdown
|
|
test libev (3.14)
cannot schedule new futures after shutdown
|
|
test libev (3.14)
cannot schedule new futures after shutdown
|
|
test libev (3.14)
cannot schedule new futures after shutdown
|
|
test asyncio (3.14t)
Process completed with exit code 1.
|
|
test asyncio (3.14t)
cannot schedule new futures after shutdown
|
|
test asyncio (3.14t)
cannot schedule new futures after shutdown
|
|
test asyncio (3.14t)
cannot schedule new futures after shutdown
|
|
test asyncio (3.14t)
cannot schedule new futures after shutdown
|
|
test asyncio (3.14t)
cannot schedule new futures after shutdown
|
|
test asyncio (3.14t)
cannot schedule new futures after shutdown
|
|
test libev (3.14t)
cannot schedule new futures after shutdown
|
|
test libev (3.14t)
cannot schedule new futures after shutdown
|
|
test libev (3.14t)
cannot schedule new futures after shutdown
|
|
test libev (3.14t)
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 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 libev (3.12)
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.11)
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 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 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 libev (3.13)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.13-pruned-9fe814fa22a73f6390d75935e5a58dd21abec8e9f73126d80173458454c1a8dd, another job may be creating this cache.
|
|
test asyncio (3.11)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.11-pruned-9fe814fa22a73f6390d75935e5a58dd21abec8e9f73126d80173458454c1a8dd, another job may be creating this cache.
|
|
test asyncio (3.13)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.13-pruned-9fe814fa22a73f6390d75935e5a58dd21abec8e9f73126d80173458454c1a8dd, another job may be creating this cache.
|
|
test asyncore (3.11)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.11-pruned-9fe814fa22a73f6390d75935e5a58dd21abec8e9f73126d80173458454c1a8dd, another job may be creating this cache.
|
|
test asyncio (3.12)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12-pruned-9fe814fa22a73f6390d75935e5a58dd21abec8e9f73126d80173458454c1a8dd, another job may be creating this cache.
|
|
test asyncio (3.14)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.14-pruned-9fe814fa22a73f6390d75935e5a58dd21abec8e9f73126d80173458454c1a8dd, another job may be creating this cache.
|