-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Closed
Labels
I-defectSomething is not working as intendedSomething is not working as intendedJ-loggingApplied to issues where logging information would help troubleshootApplied to issues where logging information would help troubleshoot
Description
What happened?
What happened:
I encountered an error while running my test suites with the command 'cucumber --tags '@smoke_1'. After executing a few success scenarios, the following error occurred:
Error:
E, [2024-02-27T09:32:17.275400 #5876] ERROR -- : unknown error: no chrome binary at C:\Program Files\Google\Chrome\Application\chrome.exe "--language-binding", "ruby", "--output", "json"]; Arg list too long - C:/Ruby33-x64/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.17.0/bin/windows/selenium-manager.exe; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location
How can we reproduce the issue?
Instructions to reproduce:
Run the test suites using the command 'cucumber --tags '@smoke_1'.
Observe the execution of the test cases.
After completing a few success scenarios, the error message as mentioned above is encountered.
Relevant log output
E, [2024-02-27T09:32:17.275400 #5876] ERROR -- : unknown error: no chrome binary at C:\\Program Files\\Google\\\Chrome\\\Application\\chrome.exe "--language-binding", "ruby", "--output", "json"]; Arg list too long - C:/Ruby33-x64/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.17.0/bin/windows/selenium-manager.exe; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location
E, [2024-02-27T14:03:43.019592 #13712] ERROR -- : FAILED ==> Unable to obtain chromedriver using Selenium Manager; Unsuccessful command executed: ["C:/Ruby33-x64/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.17.0/bin/windows/selenium-manager.exe", "--browser", "chrome", "--browser-path", "C:\\Program Files\\Google\\\Chrome\\\Application\\chrome.exe", "--language-binding", "ruby", "--output", "json"]; Arg list too long - C:/Ruby33-x64/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.17.0/bin/windows/selenium-manager.exe; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location
E, [2024-02-27T14:03:42.940160 #13712] ERROR -- : FAILED ==> GRJ462
Unable to obtain chromedriver using Selenium Manager; Unsuccessful command executed: ["C:/Ruby33-x64/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.17.0/bin/windows/selenium-manager.exe", "--browser", "chrome", "--browser-path", "C:\\Program Files\\Google\\\Chrome\\\Application\\chrome.exe", "--language-
binding", "ruby", "--output", "json"]; Arg list too long - C:/Ruby33-x64/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.17.0/bin/windows/selenium-manager.exe; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location:
Failing Scenarios:
cucumber -p required -p allure_report features/tests/E2E/E2E-1.feature:16 # Scenario: GRJ-1137
cucumber -p required -p allure_report features/tests/E2E/E2E-1.feature:31 # Scenario: GRJ-178
cucumber -p required -p allure_report features/tests/E2E/E2E-1.feature:37 # Scenario: GRJ-216
cucumber -p required -p allure_report features/tests/E2E/E2E-1.feature:51 # Scenario: GRJ-480
cucumber -p required -p allure_report features/tests/E2E/E2E-1.feature:59 # Scenario: GRJ-464
cucumber -p required -p allure_report features/tests/E2E/E2E-2.feature:15 # Scenario: GRJ-1137
cucumber -p required -p allure_report features/tests/E2E/E2E-2.feature:31 # Scenario: GRJ-339
cucumber -p required -p allure_report features/tests/E2E/E2E-2.feature:41 # Scenario: GRJ-480
cucumber -p required -p allure_report features/tests/E2E/E2E-2.feature:49 # Scenario: GRJ-464
cucumber -p required -p allure_report features/tests/E2E/E2E-3.feature:16 # Scenario: GRJ-1137
cucumber -p required -p allure_report features/tests/E2E/E2E-3.feature:31 # Scenario: GRJ-332
cucumber -p required -p allure_report features/tests/E2E/E2E-3.feature:37 # Scenario: GRJ-216
cucumber -p required -p allure_report features/tests/E2E/E2E-3.feature:52 # Scenario: GRJ-462
17 scenarios (13 failed, 4 passed)
177 steps (2 failed, 118 skipped, 57 passed)
Operating System
Windows 11
Selenium version
Ruby selenium-webdriver-4.17.0
What are the browser(s) and version(s) where you see this issue?
Chrome 121.0.6167.161
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 121.0.6167.85
Are you using Selenium Grid?
n/a
Metadata
Metadata
Assignees
Labels
I-defectSomething is not working as intendedSomething is not working as intendedJ-loggingApplied to issues where logging information would help troubleshootApplied to issues where logging information would help troubleshoot