Closed lukeis closed 8 years ago
Hi!
As i can ses there are 2 issues:
1. currently waiting with N seconds, M iterations limits for operation X seconds long
leads to real waiting of X seconds if X > N.
Your expectation is that real waiting should be N seconds.
From my point selenium works as intendent. Please create new issue for implementing
new behaviour.
2. operation execution time in grid are limited by browserTimeout preference from grid/node
configuration [1]. If your node is down or selenium is crashed any operation could
take big amount of time.
For understanding is 1700+seconds is correct or not
hub and node configuration is necessary.
[1] https://code.google.com/p/selenium/source/browse/java/server/src/org/openqa/grid/internal/TestSession.java#190
Reported by a.u.savchuk
on 2013-07-22 19:05:02
NeedsClarification
Closing the issue as there is no reproduction case provided. Feel free to ask for reopening
if it is still actual.
Reported by barancev
on 2013-10-19 22:05:10
Invalid
Reported by luke.semerau
on 2015-09-17 18:17:20
Originally reported on Google Code with ID 5691
Reported by
Daniel.K.Winsor
on 2013-05-23 18:13:51