Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Avoid using timeouts in tests if possible #358

Open
sujuka99 opened this issue Sep 12, 2023 · 0 comments
Open

Avoid using timeouts in tests if possible #358

sujuka99 opened this issue Sep 12, 2023 · 0 comments
Labels
area/tests Relates to tests low-prio Low priority issues that can be done later in the future
Milestone
Hardening KPOps

Comments

@sujuka99
Copy link
Contributor

Using a timer is not a great solution as it is highly dependent on the host. One way to mitigate false positives is to increase significantly the timeout, but that has the drawback of taking lots of time suppose the test does stall.

a timeout test

Is there any other way to consistently detect a loop?
@sujuka99 sujuka99 added area/tests Relates to tests low-prio Low priority issues that can be done later in the future labels Sep 12, 2023
@sujuka99 sujuka99 added this to the Hardening KPOps milestone Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/tests Relates to tests low-prio Low priority issues that can be done later in the future
Projects
None yet
Milestone
Hardening KPOps
Development

No branches or pull requests
1 participant
@sujuka99