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.

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

Modify test_time_tcp.py to provide more information when the test fails. #27

Closed
choksi81 opened this issue May 24, 2014 · 1 comment
Closed
Assignees

Comments

@choksi81
Copy link
Contributor

Currently the test_time_tcp.py seems to fail almost every hour due to some time descrepancy. We need to modify the test to see why its failing and/or provide more information when the test fails, so we can better understand the problem

@choksi81
Copy link
Contributor Author

Author: monzum
fixed in r3953. Modified test_time_tcp.py to provide more information on failure, such as the times that were retrieved and the servers that it connected to. It turns out that the test wasn't returning accurate results when it was sending out the notification emails. The time difference was usually around 2-3 seconds rather then the huge numbers that the notification emails claimed. I've fixed it so notification emails are sent out only if the time difference is more then 10 seconds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants