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
1 package is looking for funding
run npm fund for details
found 0 vulnerabilities
C:\Users\Ash\Downloads\0201Parking>npm install -g selenium-side-runner
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
changed 370 packages in 31s
45 packages are looking for funding
run npm fund for details
at WebDriverExecutor.getDriverSync (node_modules/@seleniumhq/side-runtime/src/webdriver.ts:173:14)
console.error
Failed to build driver for chrome
Supplied capabilities: {}
Server: none
Error: Error: Driver took too long to build. This is likely an issue with the browser or driver.
OS: win32
Node: v22.13.0
Selenium-Webdriver: 4.28.1
This is breaking at the boundary of the following code in selenium-webdriver:
// BEGIN SELENIUM-WEBDRIVER CODE
const webdriver = require('selenium-webdriver')
const driver = new webdriver.Builder().withCapabilities({}).forBrowser('chrome').build()
// END SELENIUM-WEBDRIVER CODE
To ensure the bug is in selenium IDE, please attempt to run the above code in a script or node REPL.
You may have to npm install selenium-webdriver first.
If you are unable to proceed further, please raise a bug here:
https://github.com/SeleniumHQ/selenium/issues/new?assignees=&labels=I-defect%2Cneeds-triaging&projects=&template=bug-report.yml&title=%5B%F0%9F%90%9B+Bug%5D%3A+
If this code works in selenium-webdriver, but not the IDE or side-runner, please raise a bug here:
https://github.com/SeleniumHQ/selenium-ide/issues/new?assignees=&labels=&projects=&template=bug.md
at WebDriverExecutor.getDriver (node_modules/@seleniumhq/side-runtime/src/webdriver.ts:216:17)
at WebDriverExecutor.init (node_modules/@seleniumhq/side-runtime/src/webdriver.ts:259:21)
at Object.<anonymous>.exports.default (src/connect.ts:10:3)
at Object.<anonymous> (src/main.test.ts:130:5)
Driver took too long to build. This is likely an issue with the browser or driver.
at Timeout._onTimeout (node_modules/@seleniumhq/side-runtime/src/webdriver.ts:200:13)
Test Suites: 1 failed, 1 total
Tests: 1 failed, 1 total
Snapshots: 0 total
Time: 30.97 s, estimated 31 s
Ran all test suites within paths "C:\Users\Ash\AppData\Roaming\npm\node_modules\selenium-side-runner\dist\main.test.js".
Failed to build driver for chrome
Supplied capabilities: {}
Server: none
Error: Error: Driver took too long to build. This is likely an issue with the browser or driver.
OS: win32
Node: v22.13.0
Selenium-Webdriver: 4.28.1
This is breaking at the boundary of the following code in selenium-webdriver:
// BEGIN SELENIUM-WEBDRIVER CODE
const webdriver = require('selenium-webdriver')
const driver = new webdriver.Builder().withCapabilities({}).forBrowser('chrome').build()
// END SELENIUM-WEBDRIVER CODE
To ensure the bug is in selenium IDE, please attempt to run the above code in a script or node REPL.
You may have to npm install selenium-webdriver first.
Operating System
Windows 11 Pro
Selenium version
Selenium IDE Latest
What are the browser(s) and version(s) where you see this issue?
Chrome Version 132.0.6834.84 (Official Build) (64-bit)
What are the browser driver(s) and version(s) where you see this issue?
@ADAS-Ash, thank you for creating this issue. We will troubleshoot it as soon as we can.
Info for maintainers
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!
ADAS-Ash
changed the title
[🐛 Bug]: [🐛 Bug]:
[🐛 Bug]: Failed to build driver for chrome [🐛 Bug]:
Feb 1, 2025
We have a similar issue with chrome/chromedriver on mac arm64 (java). WebDriverManager takes too long time to load the browser. Webdriver v4.26
It started to reproduce few days ago. We did not change anything in dependencies. Browser startup takes about 5min 30sec.
What happened?
Code created in Selenium IDE. Trying to use locally using command line after installing node, npm, selenium-side-runner and chrome driver.
C:\Users\Ash\Downloads\0201Parking>npm install node
added 2 packages, and audited 20 packages in 22s
1 package is looking for funding
run
npm fund
for detailsfound 0 vulnerabilities
C:\Users\Ash\Downloads\0201Parking>npm install -g selenium-side-runner
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
changed 370 packages in 31s
45 packages are looking for funding
run
npm fund
for detailsC:\Users\Ash\Downloads\0201Parking>npm install -g chromedriver
changed 60 packages in 7s
2 packages are looking for funding
run
npm fund
for detailsC:\Users\Ash\Downloads\0201Parking>selenium-side-runner -X C:\Users\Ash\Downloads\0201Parking\0201StParking.side
console.log
Beginning test session
console.info
Building driver for chrome
console.info
Driver attributes:{ capabilities: {}, server: '', browserName: 'chrome' }
console.error
FAIL ../../AppData/Roaming/npm/node_modules/selenium-side-runner/dist/main.test.js (30.881 s)
× Testing driver connection (30061 ms)
● Testing driver connection
Test Suites: 1 failed, 1 total
Tests: 1 failed, 1 total
Snapshots: 0 total
Time: 30.97 s, estimated 31 s
Ran all test suites within paths "C:\Users\Ash\AppData\Roaming\npm\node_modules\selenium-side-runner\dist\main.test.js".
How can we reproduce the issue?
Relevant log output
Operating System
Windows 11 Pro
Selenium version
Selenium IDE Latest
What are the browser(s) and version(s) where you see this issue?
Chrome Version 132.0.6834.84 (Official Build) (64-bit)
What are the browser driver(s) and version(s) where you see this issue?
132.0.6834.159 (2d77d3fc4452661469b78f115e0aed4d71269739-refs/branch-heads/6834@{#4408})
Are you using Selenium Grid?
No
The text was updated successfully, but these errors were encountered: