Skip to content

TunnelClientTests stopTriggersTunnelClose is flaky #26856

Closed
@wilkinsona

Description

@wilkinsona

We currently sleep for 200ms and then assume that the tunnel connection will have been opened once. This happens on a separate thread and is at the mercy of the OS's scheduler. We should use awaitility instead to wait for the tunnel connection to have been opened.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions