Skip to content

test: fix flaky TraceFeatureMessageRemoteWriterTest and DebuggerConfigTest#2104

Open
Anastasiia Zarechneva (zarechneva-a) wants to merge 2 commits into
developfrom
zarechneva/fix-flaky-tests
Open

test: fix flaky TraceFeatureMessageRemoteWriterTest and DebuggerConfigTest#2104
Anastasiia Zarechneva (zarechneva-a) wants to merge 2 commits into
developfrom
zarechneva/fix-flaky-tests

Conversation

@zarechneva-a

Copy link
Copy Markdown
Contributor
  • In TraceFeatureMessageRemoteWriterTest, clients now wait for TraceFeatureMessageRemoteWriter.isOpen before connecting, so they only connect after the local server is ready;
  • Added port retry handling for trace writer tests to avoid rare findAvailablePort() bind races;
  • In DebuggerConfigTest, replaced the hardcoded port with findAvailablePort() and fixed the default-port VM option lookup;
  • In debugger/trace test clients, retry now also handles Ktor SSEClientException, not only plain IOException.

closes #1252 and #1124

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

Labels

tests Add new tests or modify existing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TraceFeatureMessageRemoteWriterTest is flaky

1 participant