I am obtaining a Stainless Motorist associated mistake when operating my Selenium assessments. The problem information is “Not Able To Uncover Available Webpages.” The Selenium assessments were most operating good until final night. The issue appeared to start following a restart of the host your day before. We can’t recreate this mistake on my nearby container. Operating the Selenium assessments in the command-line about the host will available the Stainless Visitor but leads to exactly the same mistake. Any suggestions?

Point that’s faltering:

chromeDriver = new OpenQA.Selenium.Chrome.ChromeDriver(externalDriverPath);
Error communication and stacktrace:

Not able to uncover available webpages (Motorist data: chromedriver=2.1,platform=Windows NT 6.1 SP1 x86_64) at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Reaction errorResponse) at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(Chain driverCommandToExecute, Dictionary`2 guidelines) at OpenQA.Selenium.Remote.RemoteWebDriver.StartSession(ICapabilities desiredCapabilities) at OpenQA.Selenium.Remote.RemoteWebDriver.ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities) at OpenQA.Selenium.Chrome.ChromeDriver.ctor(Chain chromeDriverDirectory, ChromeOptions choices) at OpenQA.Selenium.Chrome.ChromeDriver.ctor(Chain chromeDriverDirectory) at SeleniumTests.BaseTest.SetupBrowsers()
When designing a case of the ChromeDriver, a system screen seems. The host using the mistake appears to make reference to THINGS-NOT APPLIED.


ChomeDriver Result in The Host using the Mistake:

Began ChromeDriver (v2.1) on interface 2984 [4700:4292:0108/111503:MISTAKE:gpu_info_collector_win.cc(102)] Cannot get a virginia cover WinSAT evaluation. [4700:4292:0108/111503:MISTAKE:chrome_views_delegate.cc(176)] NOT APPLIED [4700:4292:0108/111503:MISTAKE:desktop_root_window_host_win.cc(746)] NOT APPLY IMPOTENCE [0108/111504:MISTAKE:gl_surface_egl.cc(132)] eglInitialize failed using error UNKNO WN [0108/111504:MISTAKE:gl_surface_win.cc(97)] GLSurfaceEGL::InitializeOneOff unsuccessful.
ChomeDriver Result From Our Computer which functions good:

Began ChromeDriver (v2.1) on interface 18786 [884540:883760:0108/114010:MISTAKE:gpu_info_collector_win.cc(102)] Cannot get a legitimate WinSAT evaluation. [884992:884996:0108/114010:MISTAKE:base_feature_provider.cc(122)] manifestTypes: A llowing web_page contexts demands offering a price for fits. [885232:885236:0108/114011:MISTAKE:base_feature_provider.cc(122)] manifestTypes: A llowing web_page contexts demands offering a price for fits. [884540:883760:0108/114011:MISTAKE:base_feature_provider.cc(122)] manifestTypes: A llowing web_page contexts demands offering a price for fits. [0108/114011:MISTAKE:gl_surface_egl.cc(131)] eglInitialize failed using error UNKNO WN [0108/114011:MISTAKE:gl_surface_win.cc(54)] GLSurfaceEGL::InitializeOneOff unsuccessful.
You’re utilizing a extremely obsolete edition of the ChromeDriver. The initial port-of-call ought to be to revise it below.

I’d extremely believe the thing is your Stainless in your host offers updated, and ChromeDriver v2.1 does not help any current variations of Stainless.

I’d exactly the same issue, but upgrading towards the newest ChromeDriver (v2.8) didn’t resolve it for me personally. I had been operating Selenium on the CI host (A Dell device operating 64-bit Get SEVEN). I acquired the exclusion each time once the host have been Anonproductive’ for some time.
What set the issue for me personally was to create ‘turn fully off show after’ in Windows’ Energy Choices to ‘Never’.

———-ChromeDriver v2.8 (2013-12-16)———-
Facilitates Stainless v30-33
Solved problem 638: Chomedriver 2.7, signing nevertheless damaged. [Pri-0]
Solved problem 507: Dessert development – Site obtaining prefixed having a time INCH.” [Pri-0]
Solved problem 516: Plug-Ins using _generated_background_page no further launching in 2.3 [Pri-0]
Solved problem 405: Cannot kind several no-ascii figures [OS-Windows, Pri-0]
Solved problem 627: Having A keyboard format!EQUALS people send_keys doesn’t deliver several numbers figures (0, TWO, SEVEN, NINE) [OS-Linux, Pri-0]

———-ChromeDriver v2.7 (2013-11-22)———-
Facilitates Stainless v30-33
Solved problem 615: ChromeDriver fails nicely using car identify proxy configurations [OS-Windows, Pri-0]
Solved problem 614: Apply fresh redirectionless ORprogram order [Pri-0]
Solved problem 625: signing damaged on windows [Pri-0]
Solved problem 573: chromedriver failures on windows periodically [OS-Windows, Pri-INCH]

———-ChromeDriver v2.6 (2013-11-04)———-
Facilitates Stainless v29-32
Solved problem 599: Chromedriver failes after MacOS X Mavericks update [OS-Macintosh, Pri-0, Kind-Deficiency]
Solved problem 585: Reunite person information dir via abilities []

———-ChromeDriver v2.5 (2013-11-01)———-
Facilitates Stainless v29-32
Solved problem 600: Assistance minidump regarding stainless failures on Linux having a new capacity minidump_path. [Pri-0]
Solved problem 569: a big change in flash smashes scrolling a component into see [Pri-0]
Solved problem 554: release-notes damaged [Pri-0]
Solved problem 545: dangle when debugger is invoked via JS [Pri-0]

———-ChromeDriver v2.4 (2013-09-30)———-
Facilitates Stainless v29-32
Solved problem 444: chromedriver occasionally weighs when starting stainless (stainless does not hole to debug interface) [Pri-0]
Solved problem 529: WebDriver customers crash when trying to utilize vacant chromeOption binary chain [Pri-0]
Solved problem 536: rural debugging interface obtained during medical [Pri-0]
Solved problem 520: Several instructions dangles when the goal screen currently failures. []
Solved problem 519: Assistance JS pile overview []

———-ChromeDriver v2.3 (2013-09-02)———-
Solved problem 309: Screenshot is empty from an VM occasion with no available RDC link [Pri-INCH]
Solved problem 445: chromedriver failures when interface is being used [Pri-INCH]
Solved problem 461: touch-up, landing, and TouchMove instructions [OS-Most, Pri-INCH]
Solved problem 489: no further utilizing loaded expansion identification when launching customized exts [Pri-THREE]
Solved problem 491: Expansion doesn’t possess its _id_ [Pri-THREE]
Solved problem 497: unrecognized stainless choice: useExistingBrowser [Pri-THREE]

———-ChromeDriver v2.2 (2013-08-06)———-

Leave a Reply

Your email address will not be published. Required fields are marked *