Retry session
We've found with CircleCI that we randomly received timeouts when using standalone selenium Chrome instance.
From time to time these timeouts occur more often and seem to randomly disappear again. My suspicion is that the networking of CircleCI (I believe they use AWS) cannot be relied upon to disable the timeouts in the tests.
Is there a particular reason why the start of the session is not retried?
Thank you, and sorry for the delay. I am not sure why we did not retry in the first place, so let's see if @HashNuke can help us out here.
I would very much like this fixed as well if there's not a reason for the retries being stripped out. it also affects my use case