You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: