Skip to content

Comments

Fix flaky test_no_connection_refused_on_timeout#710

Draft
dkropachev wants to merge 1 commit intomasterfrom
fix-flaky-lwt-timeout-test
Draft

Fix flaky test_no_connection_refused_on_timeout#710
dkropachev wants to merge 1 commit intomasterfrom
fix-flaky-lwt-timeout-test

Conversation

@dkropachev
Copy link
Collaborator

@dkropachev dkropachev commented Feb 22, 2026

Summary

  • Fix flaky LightweightTransactionTests::test_no_connection_refused_on_timeout that fails when all LWT operations complete before the default timeout on fast CI runners
  • Use a very short client-side request timeout (0.0001s) via ExecutionProfile to guarantee OperationTimedOut exceptions occur
  • Add OperationTimedOut to the list of accepted timeout exception types alongside server-side WriteTimeout/WriteFailure

Test plan

  • CI integration tests pass with libev reactor
  • CI integration tests pass with asyncio reactor

@dkropachev dkropachev force-pushed the fix-flaky-lwt-timeout-test branch from 1e12be2 to f4f77a3 Compare February 22, 2026 14:52
@dkropachev dkropachev self-assigned this Feb 22, 2026
@dkropachev dkropachev force-pushed the fix-flaky-lwt-timeout-test branch 2 times, most recently from c1266b9 to 7417654 Compare February 22, 2026 20:14
The test relies on LWT operations producing at least one timeout, but on
fast CI runners all operations may complete before the default 10s timeout,
causing `assert received_timeout` to fail.

Fix by using a very short client-side request timeout (0.0001s) via an
ExecutionProfile, which guarantees OperationTimedOut exceptions. Also add
OperationTimedOut to the list of accepted timeout exception types so the
test correctly recognizes client-side timeouts alongside server-side
WriteTimeout/WriteFailure.
@dkropachev dkropachev force-pushed the fix-flaky-lwt-timeout-test branch from 7417654 to 2d5edf7 Compare February 22, 2026 22:01
@dkropachev dkropachev marked this pull request as draft February 22, 2026 22:01
@dkropachev
Copy link
Collaborator Author

Needs - #716 and #713

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant