Self review. Whatever the timeout was set at before, it was having almost no effect because even a 300 second timeout would not result in a session getting picked up. And when it did time out, the test would just be skipped and we'd not know.
I increased it to 60 because just in case a test method does get stuck waiting we don't want tests to fail, but don't really want to set it higher because if we do get a similar or similar-ish problem with selenium again, I think we'd want to see the timeouts happen and not wait for minute. We can always tweak this later.
Self review. Whatever the timeout was set at before, it was having almost no effect because even a 300 second timeout would not result in a session getting picked up. And when it did time out, the test would just be skipped and we'd not know.
I increased it to 60 because just in case a test method does get stuck waiting we don't want tests to fail, but don't really want to set it higher because if we do get a similar or similar-ish problem with selenium again, I think we'd want to see the timeouts happen and not wait for minute. We can always tweak this later.