Hi all
can somebody give hints what could be causing "Cannot start session..." error?
It occasionally happens on BrowserStack and it is even not reproducible on same browser (I've checked this with their support). There are no errors in the server log and this really happens randomly (let's say in 1% of tests).
Screenshot of the error:
https://s3.amazonaws.com/testautomation/1a3e77730463a9689027d5edb2a02f1faa9f...
I'm wondering if we don't send out some bad mixture of headers which can cause such random problems on the way (eg. on some proxy).
Le 2014-02-19 13:41, Michal Čihař a écrit :
Hi all
can somebody give hints what could be causing "Cannot start session..." error?
It occasionally happens on BrowserStack and it is even not reproducible on same browser (I've checked this with their support). There are no errors in the server log and this really happens randomly (let's say in 1% of tests).
Screenshot of the error:
https://s3.amazonaws.com/testautomation/1a3e77730463a9689027d5edb2a02f1faa9f...
I'm wondering if we don't send out some bad mixture of headers which can cause such random problems on the way (eg. on some proxy).
Hi Michal, to debug this, does BrowserStack offer a packet capture facility?
Hi
Dne Thu, 20 Feb 2014 06:08:08 -0500 Marc Delisle marc@infomarc.info napsal(a):
Le 2014-02-19 13:41, Michal Čihař a écrit :
Hi all
can somebody give hints what could be causing "Cannot start session..." error?
It occasionally happens on BrowserStack and it is even not reproducible on same browser (I've checked this with their support). There are no errors in the server log and this really happens randomly (let's say in 1% of tests).
Screenshot of the error:
https://s3.amazonaws.com/testautomation/1a3e77730463a9689027d5edb2a02f1faa9f...
I'm wondering if we don't send out some bad mixture of headers which can cause such random problems on the way (eg. on some proxy).
Hi Michal, to debug this, does BrowserStack offer a packet capture facility?
No, but I could probably log this at the server. On the other side, the error seems to be gone now without doing any fixes, so there is probably no way to debug it further...
-
Marc Delisle -
Michal Čihař