Closed gheeno closed 1 year ago
@gheeno, thank you for creating this issue. We will troubleshoot it as soon as we can.
Triage this issue by using labels.
If information is missing, add a helpful comment and then I-issue-template
label.
If the issue is a question, add the I-question
label.
If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted
label.
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable G-*
label, and it will provide the correct link and auto-close the
issue.
After troubleshooting the issue, please add the R-awaiting answer
label.
Thank you!
Can you run with 4.7? We improved the error message for that error.
@titusfortner , updated dependency to 4.7 and reran the smoke test.
Still the same observation as 4.6
java.lang.IllegalStateException: The path to the driver executable The path to the driver executable must be set by the webdriver.chrome.driver system property; for more information, see https://chromedriver.chromium.org/. The latest version can be downloaded from https://chromedriver.chromium.org/downloads
at org.openqa.selenium.internal.Require$StateChecker.nonNull(Require.java:314)
at org.openqa.selenium.remote.service.DriverService.findExecutable(DriverService.java:148)
at org.openqa.selenium.chrome.ChromeDriverService.access$000(ChromeDriverService.java:39)
at org.openqa.selenium.chrome.ChromeDriverService$Builder.findDefaultExecutable(ChromeDriverService.java:233)
at org.openqa.selenium.remote.service.DriverService$Builder.build(DriverService.java:450)
at org.openqa.selenium.chrome.ChromeDriverService.createServiceWithConfig(ChromeDriverService.java:142)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:70)
at com.core.factory.webdriver.DriverSettings.startDefaultDriver(DriverSettings.java:51)
at com.core.factory.webdriver.DriverActions.openBrowser(DriverActions.java:51)
at com.pos.stepdefinitions.steps.common.WindowHandlerSteps.openBrowser(WindowHandlerSteps.java:22)
at ✽.a default browser is opened(file:///apps/jenkins/slave/workspace/Automation/Tools%20-%20Feature%20Branch%20Smoke%20Test/src/test/java/com/features/cbo/boui/DeviceOverviewService.feature:5)
Right, there should be something more on this line in 4.7:
10:34:49.999 [pool-1-thread-1] WARN o.o.s.remote.service.DriverService - Unable to obtain driver using Selenium Manager: Error running command: [/tmp/selenium-manager20252854139289024732448555598337657/selenium-manager, --driver, chromedriver]
@titusfortner , used 4.7 here
[INFO] Running SMOKE TEST - MKS - Employee Sale
14:53:52.831 [pool-1-thread-8] INFO o.s.b.t.c.SpringBootTestContextBootstrapper - Neither @ContextConfiguration nor @ContextHierarchy found for test class [com.core.config.SpringTestConfig], using SpringBootContextLoader
14:53:52.837 [pool-1-thread-8] INFO o.s.t.c.s.AbstractContextLoader - Could not detect default resource locations for test class [com.core.config.SpringTestConfig]: no resource found for suffixes {-context.xml, Context.groovy}.
14:53:53.052 [pool-1-thread-8] INFO o.s.b.t.c.SpringBootTestContextBootstrapper - Loaded default TestExecutionListener class names from location [META-INF/spring.factories]: [org.springframework.boot.test.mock.mockito.MockitoTestExecutionListener, org.springframework.boot.test.mock.mockito.ResetMocksTestExecutionListener, org.springframework.boot.test.autoconfigure.restdocs.RestDocsTestExecutionListener, org.springframework.boot.test.autoconfigure.web.client.MockRestServiceServerResetTestExecutionListener, org.springframework.boot.test.autoconfigure.web.servlet.MockMvcPrintOnlyOnFailureTestExecutionListener, org.springframework.boot.test.autoconfigure.web.servlet.WebDriverTestExecutionListener, org.springframework.boot.test.autoconfigure.webservices.client.MockWebServiceServerTestExecutionListener, org.springframework.test.context.web.ServletTestExecutionListener, org.springframework.test.context.support.DirtiesContextBeforeModesTestExecutionListener, org.springframework.test.context.event.ApplicationEventsTestExecutionListener, org.springframework.test.context.support.DependencyInjectionTestExecutionListener, org.springframework.test.context.support.DirtiesContextTestExecutionListener, org.springframework.test.context.transaction.TransactionalTestExecutionListener, org.springframework.test.context.jdbc.SqlScriptsTestExecutionListener, org.springframework.test.context.event.EventPublishingTestExecutionListener]
14:53:53.083 [pool-1-thread-8] INFO o.s.b.t.c.SpringBootTestContextBootstrapper - Using TestExecutionListeners: [org.springframework.test.context.support.DirtiesContextBeforeModesTestExecutionListener@618e0ec8, org.springframework.test.context.event.ApplicationEventsTestExecutionListener@317d6e22, org.springframework.boot.test.mock.mockito.MockitoTestExecutionListener@30fbe6e9, org.springframework.boot.test.autoconfigure.SpringBootDependencyInjectionTestExecutionListener@7796ade9, org.springframework.test.context.support.DirtiesContextTestExecutionListener@667f059d, org.springframework.test.context.transaction.TransactionalTestExecutionListener@3c296b0e, org.springframework.test.context.jdbc.SqlScriptsTestExecutionListener@530a1ecc, org.springframework.test.context.event.EventPublishingTestExecutionListener@11b108a1, org.springframework.boot.test.mock.mockito.ResetMocksTestExecutionListener@ffcb4e7, org.springframework.boot.test.autoconfigure.restdocs.RestDocsTestExecutionListener@787adf0d, org.springframework.boot.test.autoconfigure.web.client.MockRestServiceServerResetTestExecutionListener@7b8542b0, org.springframework.boot.test.autoconfigure.web.servlet.MockMvcPrintOnlyOnFailureTestExecutionListener@62e8a961, org.springframework.boot.test.autoconfigure.web.servlet.WebDriverTestExecutionListener@8597257, org.springframework.boot.test.autoconfigure.webservices.client.MockWebServiceServerTestExecutionListener@26f556e6]
@smoke
Scenario: Return Transaction - non-receipted return # src/test/java/com/features/tools/smoke/Mks_Smoke.feature:9
14:53:55.993 [pool-1-thread-8] INFO c.pos.stepdefinitions.CucumberHooks - Thread - 19 - Scenario - Return Transaction - non-receipted return
14:53:56.154 [pool-1-thread-8] WARN o.o.s.remote.service.DriverService - Unable to obtain driver using Selenium Manager: Unsuccessful command executed: [/tmp/selenium-manager20408319189877774246851600088809023/selenium-manager, --driver, chromedriver]
/tmp/selenium-manager20408319189877774246851600088809023/selenium-manager: /lib64/libc.so.6: version `GLIBC_2.29' not found (required by /tmp/selenium-manager20408319189877774246851600088809023/selenium-manager)
/tmp/selenium-manager20408319189877774246851600088809023/selenium-manager: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/selenium-manager20408319189877774246851600088809023/selenium-manager)
/tmp/selenium-manager20408319189877774246851600088809023/selenium-manager: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/selenium-manager20408319189877774246851600088809023/selenium-manager)
/tmp/selenium-manager20408319189877774246851600088809023/selenium-manager: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /tmp/selenium-manager20408319189877774246851600088809023/selenium-manager)
Build info: version: '4.7.0', revision: '0a5b49d16f'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-1160.76.1.el7.x86_64', java.version: '1.8.0_275'
Driver info: driver.version: ChromeDriver
Given a default browser is opened # com.pos.stepdefinitions.steps.common.WindowHandlerSteps.openBrowser()
java.lang.IllegalStateException: The path to the driver executable The path to the driver executable must be set by the webdriver.chrome.driver system property; for more information, see https://chromedriver.chromium.org/. The latest version can be downloaded from https://chromedriver.chromium.org/downloads
at org.openqa.selenium.internal.Require$StateChecker.nonNull(Require.java:314)
at org.openqa.selenium.remote.service.DriverService.findExecutable(DriverService.java:148)
at org.openqa.selenium.chrome.ChromeDriverService.access$000(ChromeDriverService.java:39)
at org.openqa.selenium.chrome.ChromeDriverService$Builder.findDefaultExecutable(ChromeDriverService.java:233)
at org.openqa.selenium.remote.service.DriverService$Builder.build(DriverService.java:450)
at org.openqa.selenium.chrome.ChromeDriverService.createServiceWithConfig(ChromeDriverService.java:142)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:70)
at com.core.factory.webdriver.DriverSettings.startDefaultDriver(DriverSettings.java:51)
at com.core.factory.webdriver.DriverActions.openBrowser(DriverActions.java:51)
at com.pos.stepdefinitions.steps.common.WindowHandlerSteps.openBrowser(WindowHandlerSteps.java:22)
at ✽.a default browser is opened(file:///apps/jenkins/slave/workspace/Automation/Tools%20-%20Feature%20Branch%20Smoke%20Test/src/test/java/com/features/tools/smoke/Mks_Smoke.feature:5)
@diemol maybe some CI environments don't give the execution permissions in temp directories?
Maybe this is the real use case for #11359?
I'll defer to what @bonigarcia thinks, because if @gheeno says that it works with WebDriverManager, then we might be missing something there.
These traces shows the cause of the issue:
14:53:56.154 [pool-1-thread-8] WARN o.o.s.remote.service.DriverService - Unable to obtain driver using Selenium Manager: Unsuccessful command executed: [/tmp/selenium-manager20408319189877774246851600088809023/selenium-manager, --driver, chromedriver]
/tmp/selenium-manager20408319189877774246851600088809023/selenium-manager: /lib64/libc.so.6: version `GLIBC_2.29' not found (required by /tmp/selenium-manager20408319189877774246851600088809023/selenium-manager)
It seems that the selenium-manager
binary cannot be executed in your Linux because of the glibc
version. For the upcoming releases of Selenium Manager, we can try prevent this problem by linking statically the Rust binary (e.g. see reference).
@gheeno For trying to solve the issue in Selenium 4.7, you can try to update your glibc
to version 2.29, as follows:
sudo apt install libc-bin=2.29 libc6=2.29
@bonigarcia thanks for the feedback. I'll probably wait for 4.8
, our we use RedHat 7 and it's limited to 2.19
.
I'll use your WebDriverManager in the time meantime.
Thanks, team.
I have just created a PR (#11471) to prevent this issue in the upcoming versions of Selenium Manager.
@gheeno Is it possible you try this at your end, please? To do that, download following Selenium Manager binary: selenium-manager_linux-x64, uncompress it in the machine you experienced the issue (your Jenkins), and execute the following:
./selenium-manager --browser chrome --debug
Please let us know if the issue has been fixed with that binary, thanks.
I have just created a PR (#11471) to prevent this issue in the upcoming versions of Selenium Manager.
@gheeno Is it possible you try this at your end, please? To do that, download following Selenium Manager binary: selenium-manager_linux-x64, uncompress it in the machine you experienced the issue (your Jenkins), and execute the following:
./selenium-manager --browser chrome --debug
Please let us know if the issue has been fixed with that binary, thanks.
For sure. I am currently on vacation for a week. I’ll execute it when I get back. January 3 2023.
Thanks for looking into this!
Have a great holiday season.
What happened?
Issue : java.lang.IllegalStateException: The path to the driver executable The path to the driver executable must be set by the webdriver.chrome.driver system property
Steps :
Results :
POM :
Note :
Running the same test locally, after deleting all the initial webdrivers, it runs fine. Local machine spec: MacOS Ventura ( intel chip )
Running 4.6.0 with Bonni's WebDriverManager in Jenkins ( Linux )
Environments
Selenium 4.6.0 / 4.7.0( without Boni's webDriverManager )
Selenium 4.6.0 ( with Boni's webDriverManager )
How can we reproduce the issue?
Relevant log output
Operating System
Linux ( Jenkins ) , macOS Ventura ( Local )
Selenium version
4.6.0 , 4.7.0
What are the browser(s) and version(s) where you see this issue?
Chrome 87
What are the browser driver(s) and version(s) where you see this issue?
Chrome 87, Chrome 108
Are you using Selenium Grid?
No