[INTTEST-15] Make sure test timers are set accordingly to ODL documentation Created: 05/Jun/17 Updated: 19/Oct/17 Resolved: 26/Jun/17 |
|
| Status: | Resolved |
| Project: | integration-test |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Peter Gubka |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
The most suites were already fixed when examining various failures, but there still are some leftovers to be fixed. This mainly applies to Http reads: Tell-based protocol may take up to 120 seconds before giving up on a request, so Robot should use 125 second timeout. This also concerns Jolokia reads (usually when locating leader and followers) when there is large amount of transactions to process. The Jolokia itself has no upper bound, but Robot should wait 125 seconds to make sure data requests are failing already. |
| Comments |
| Comment by Vratko Polak [ 05/Jun/17 ] |
| Comment by Vratko Polak [ 05/Jun/17 ] |
|
Another place: 05:02:41 ReadTimeout: HTTPConnectionPool(host='10.29.14.228', port=8181): Read timed out. (read timeout=30.0) |
| Comment by Vratko Polak [ 20/Jun/17 ] |
|
Additional places show up when unrelated fixes are merged: [2]. |
| Comment by Peter Gubka [ 26/Jun/17 ] |