CI: end-to-end connector tests time out when the runner host is saturated #78
Labels
No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
natsukium/felis#78
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Push-event run 1646 on main (
03d56ca7, a BREAKING.md-only change) failed in cargo nextest:connector::tests::window_client_hears_session_exited_when_shell_exitshit its 15 s deadline (crates/felis-client-core/src/connector.rs:2844) and reportedleft: None. The same SHA passed the pull_request run minutes earlier. The runner is the host that also builds the implementation workflows; its one-minute load average was around 42 on 12 cores at the time. The Criterion regression gate reported phantom +17% to +51% regressions on a comment-only PR (#76) under the same load. The bench gate now withholds its verdict on a saturated host; the deadline-based daemon tests have no such guard. Options: scale the deadlines by load, serialize the test job behind other runner work, or accept the flake and rerun. Not a code regression.