Skip to content

Conversation

@clalancette
Copy link
Contributor

In commit 0c081a7 (#360) we increased the timeout to 10 seconds to accomodate slower discovery. However, this was partially reverted in
2d125a5
(#353).

Restore the 10 second timeout to avoid flakes on the buildfarm.

In commit 0c081a7
(#360) we increased
the timeout to 10 seconds to accomodate slower discovery.
However, this was partially reverted in
2d125a5
(#353).

Restore the 10 second timeout to avoid flakes on the
buildfarm.

Signed-off-by: Chris Lalancette <clalancette@gmail.com>
@clalancette
Copy link
Contributor Author

CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status
@clalancette clalancette merged commit a26e13a into rolling Aug 28, 2023
@clalancette clalancette deleted the clalancette/wait-for-topics-test-increase-timeout branch August 28, 2023 13:29
@Ryanf55
Copy link

Ryanf55 commented Feb 21, 2024

Is there a more "robust" way to do this in CI without hard-coded delay? 10 seconds seems pretty long for a single discovery channel, no?

We're facing the same issues with the delays in internal CI, except it's dropping samples and causing test failures in our system tests, which hang up our release pipelines to prod.

More context on related issue:
#356 (comment)

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

Labels

None yet

4 participants