kubernetes-client / kubernetes-client/java
[Umbrella Issue] Many tests use Thread.sleep instead of synchronization primitives
Open
good first issue
lifecycle/frozen
- Dominant language
- Java
- Stars
- 4k
- Forks
- 2.1k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 16
Description
Many of our tests simply have a `Thread.sleep(duration)` when testing multi-threaded code. This is inherently flaky.
Instead we should use synchronization classes (generally `Semaphore`) to synchronized the tests which is both faster in the general case and not flaky in the extreme case.
See for instance #1218 and #1219
Contributor guide
Assessment
This issue has not been assessed yet.