This repository has been archived by the owner on Jul 16, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 51
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
testutil: use consistent timeout for results channels
These timeouts "should never trigger", but if they do we get a test failure sooner than waiting for go test's very long timeout. The 25 second number isn't special. And it's known to possibly be too short for example in the case of TestReconnects(), where the ssntp client incurs a series of delays that are 0..5, 0..10, 0..20, 0..40 seconds. If the server is slow in restarting it _might_ take 4 seconds to restart in travis. But worst case we hit client delays of 1,1,1,40 seconds. In which case despite everything "working correctly" the test case will timeout for lack of NodeConnected result after 25s, when it would be coming at 43s. Signed-off-by: Tim Pepper <[email protected]>
- Loading branch information
Tim Pepper
committed
Aug 19, 2016
1 parent
b2ea19b
commit 4fb5889
Showing
3 changed files
with
11 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters