Selenium Grid + Jenkins: "unable to discover open pages"

[Matthias Berg]

Hi,

I cannot get selenium grid to work in our environment.
selenium-java-2.45.0.jar
selenium-server-standalone-2.45.0.jar

We run the hub on a jenkins master and the node on a jenkins slave with windows 7.
if I log in on the slave and start the node with a command line call, then the test cases work.
letting the buildjob start the node on the slave with the command line call does not work. I read something about some session 0 issue. Maybe this is the problem here as well?

12:32:13     [junit] Failure in before hook:BaseStepDefinitions.beforeTest()
12:32:13     [junit] Message: org.openqa.selenium.WebDriverException: unknown error: unable to discover open pages
12:32:13     [junit]   (Driver info: chromedriver=2.22.397933 (1cab651507b88dec79b2b2a22d1943c01833cc1b),platform=Windows NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
12:32:13     [junit] Command duration or timeout: 60.66 seconds
12:32:13     [junit] Build info: version: '2.53.0', revision: '35ae25b', time: '2016-03-15 17:00:58'
12:32:13     [junit] System info: host: 'CI-02-SLAVE-07', ip: '172.22.202.50', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.8.0_101'
12:32:13     [junit] Driver info: org.openqa.selenium.chrome.ChromeDriver
12:32:13     [junit] Command duration or timeout: 62.16 seconds
12:32:13     [junit] Build info: version: '2.45.0', revision: '5017cb8', time: '2015-02-27 00:00:10'
12:32:13     [junit] System info: host: 'CI-02-SLAVE-07', ip: '172.22.202.50', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.8.0_101'
12:32:13     [junit] Driver info: org.openqa.selenium.remote.RemoteWebDriver
12:32:13     [junit] 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
12:32:13     [junit] 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
12:32:13     [junit] 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
12:32:13     [junit] 	at java.lang.reflect.Constructor.newInstance(Unknown Source)

The other idea was to let the node start on startup and let the user logged in all the time (not a solution that is good, but if we have to do, we could do it).
Here the problem was that the second run would not work because the workspace could not be cleaned. I think some temporary file from chrome driver was blocking it.
In the after methode we have:
        driver.close();
        driver.quit();
So it surprises me a bit, that there is still some open file handler. if we kill the java process, the handler is gone.

Kind regards,
Matthias Berg

[⇜Krishnan Mahadevan⇝]

Matthias,

The latest released version of Selenium is 2.53.1

Please see my response here : http://stackoverflow.com/a/38721806/679824

Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/

My Technical Scribbings @ http://rationaleemotions.wordpress.com/

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To post to this group, send email to seleniu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/0739a16a-1b97-4293-82a3-9cc4d597b168%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Matthias Berg]

Hello,
we managed to put the temp files into another folder so that the workspace can be deleted. As far as I saw the temp files problem might be fixed in the latest jenkins version (somewhere in may 2016), but we won't switch to it really soon, but during the next few months hopefully.
I'm using 2.53.1 now (am I right to think that switching to 3 is not that easy?).
We are using the no-sandbox flag now.
------------------
    ChromeOptions options = new ChromeOptions();
            options.addArguments("no-sandbox");
            DesiredCapabilities capabilities = DesiredCapabilities.chrome();
            capabilities.setCapability(ChromeOptions.CAPABILITY, options);
            capabilities.setBrowserName("chrome");
-----------------
starting the grid node on startup works for us now, but it just means that we need to always login a user which may not be that easy with a domain computer and the people accessing should keep in mind to not logout. In  a windows session it still does not work (30 or 40 out of 80 TCs fail).
I guess I can live with our current solution, but it's still not perfect.
thanks

Matthias