Skip to content

Conversation

@mp911de
Copy link
Member

@mp911de mp911de commented Feb 17, 2016

Several tests rely heavily on time to perform synchronization. This leads to an increased test duration and in some cases to failed tests. In some cases time is the only possibility to attempt synchronization.

Remove Thread.sleep from tests which do not require a sleep at all. Use a condition where possible. Increase timeouts on tests known to fail very likely due to a short Thread.sleep.

Several tests rely heavily on time to perform synchronization. This leads to an increased test duration and in some cases to failed test. In some cases time is the only possibility to attempt synchronization. Remove Thread.sleep from tests which do not require a sleep at all. Use a condition where possible. Increase timeouts on tests known to fail very likely due to a short Thread.sleep.
christophstrobl pushed a commit that referenced this pull request Feb 18, 2016
Several tests rely heavily on time to perform synchronization. Therfore we remove Thread.sleep from tests which do not require a sleep at all, use a condition where possible and increase timeouts on tests known to fail very likely due to a short Thread.sleep. Original Pull Request: #171
@christophstrobl christophstrobl deleted the issue/DATAREDIS-463 branch February 18, 2016 07:08
christophstrobl pushed a commit that referenced this pull request Feb 22, 2016
Several tests rely heavily on time to perform synchronization. Therfore we remove Thread.sleep from tests which do not require a sleep at all, use a condition where possible and increase timeouts on tests known to fail very likely due to a short Thread.sleep. Original Pull Request: #171
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants