Skip to content

Fix on_up() destroying healthy pool after replace-with-same-IP #2462

Fix on_up() destroying healthy pool after replace-with-same-IP

Fix on_up() destroying healthy pool after replace-with-same-IP #2462

Triggered via pull request June 4, 2026 14:13
Status Success
Total duration 21m 8s
Artifacts

integration-tests.yml

on: pull_request
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

23 errors
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 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.14t)
cannot schedule new futures after shutdown
test libev (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 asyncore (3.11)
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.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