You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there -- we recently setup the Sauce + Grid plugin so that we could use sauce to handle all of our browser testing needs. Everything was working quite well until yesterday...(coincidentally, around the time that the cookie error states in the logs)
Basically, what happens is that a test will run...it will spin up the VM...and then the VM will just sit there...like it will not accept any commands.
So, the test times out, and we get an error.
Here's what our server logs look like (notice the warning about the cookie...this seems to be about the same time that stuff started breaking) http://bit.ly/11gmqhc
(ive since changed the access key, for security reasons)
Here's what i see on my machine when i kick off the tests against our grid: (notice the 302 error)
As far as a server setup goes, basically, we are pretty much following the directions stated in the blog post / your github account. We've got the jars in the same directory, and ar running this command
From there, im connecting to our hub as such from our tests:
desired_capabilities=webdriver.DesiredCapabilities.CHROME#leaving this blank for chromedesired_capabilities['version'] =''desired_capabilities['platform'] ='Windows 2008'#set the test name to the name of this class, so we know which it is.desired_capabilities['name'] =self.__class__.__name__desired_capabilities['idle-timeout'] =30self.driver=webdriver.Remote(
command_executor="http://selenium00.dev.ourdomain.net:4444/wd/hub",
desired_capabilities=desired_capabilities
)
the tests run fine against Sauce (ruling out the possibility that it's my tests that are the issue). seems to definitely be an issue with hub / the plugin.
just trying to give you as much data as possible...thanks again for looking into this!
Hi, I'm really sorry for not replying to this issue earlier - I only just spotted it now...is this still an issue for you? I vaguely recall that it got resolved a while ago, but please let me know if it's still a problem when using the latest version of the plugin.
Hey there -- we recently setup the Sauce + Grid plugin so that we could use sauce to handle all of our browser testing needs. Everything was working quite well until yesterday...(coincidentally, around the time that the cookie error states in the logs)
Basically, what happens is that a test will run...it will spin up the VM...and then the VM will just sit there...like it will not accept any commands.
So, the test times out, and we get an error.
Here's what our server logs look like (notice the warning about the cookie...this seems to be about the same time that stuff started breaking)
http://bit.ly/11gmqhc
(ive since changed the access key, for security reasons)
Here's what i see on my machine when i kick off the tests against our grid: (notice the 302 error)
http://pastie.org/private/sqlqle8pkfnpf9bctripmw
Some URLs to a few random timing out tests...
https://saucelabs.com/tests/aed82e50260f4e669cecbf581df7be49
https://saucelabs.com/tests/0c043fc226c74530b8e9b44daa286ffa
https://saucelabs.com/tests/2d109f1457e14eedb5346d8ceaa9cefe
https://saucelabs.com/tests/f7849dcccdc84a94acb8ee37078b81bd
As far as a server setup goes, basically, we are pretty much following the directions stated in the blog post / your github account. We've got the jars in the same directory, and ar running this command
From there, im connecting to our hub as such from our tests:
Thanks for any help!
-kasey
[email protected]
The text was updated successfully, but these errors were encountered: