Share
Go down
grgr
Posts : 1
Join date : 2017-06-07

chromedriver.exe does not start

on Wed Jun 07, 2017 4:33 am
I have:

  • Windows 10 64 bit
  • Chrome version 58
  • Node 6.10.1
  • Npm 3.10.10
  • chromedriver 2.29.0

Selenium standalone is run but after running my tests (with Chrome) there is an error in the console where selenium was run:

Code:
os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_73'
Driver info: driver.version: unknown
        at java.util.concurrent.FutureTask.report(Unknown Source)
        at java.util.concurrent.FutureTask.get(Unknown Source)
        at org.openqa.selenium.remote.server.DefaultSession.execute(DefaultSession.java:183)
Caused by: org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start.
Build info: version: '3.4.0', revision: 'unknown', time: 'unknown'
System info: host: 'FAB-CL-F0C1J72', ip: '10.240.2.127', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_73'
Driver info: driver.version: ChromeDriver
        at org.openqa.selenium.remote.service.DriverService.waitUntilAvailable(DriverService.java:193)
        at org.openqa.selenium.remote.service.DriverService.start(DriverService.java:181)
        at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:78)
        at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:637)
        at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:250)
        at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:236)
        at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:137)
        at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:184)
        at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:148)
        ... 14 more
Caused by: org.openqa.selenium.net.UrlChecker$TimeoutException: Timed out waiting for [localhost :5373/ status] to be available after 20002 ms

in the second console where tests are run i got:
chrome
Error: An unknown server-side error occurred while processing the command. (UnknownError:13)

I tried with different versions node.js and npm but it did not help. I tried also with webdriver-manager instead of selenium-standalone server
when I change Firefox into Chrome FF browser is opened..
Earlier it worked with Chrome... but stopped. I do not know why (another person's work, and they have similar versions now).

chromedriver.exe and CHROME browser are the newest

 

Code:
const getStoreUrl = require("./getStoreUrl");


const setSeleniumHost = require("./setSeleniumHost");


 


exports.config = {


 


    //


    // ==================


    // Specify Test Files


    // ==================


    // Define which test specs should run. The pattern is relative to the directory


    // from which `wdio` was called. Notice that, if you are calling `wdio` from an


    // NPM script ) then the current working


    // directory is where your package.json resides, so `wdio` will be called from there.


    //





    suites: {


 


        otherFeature: [
            // ...
        ],


    },


 


    host: setSeleniumHost(),


    port: 4444,


 


 


    //


    // ============


    // Capabilities


    // ============


    // Define your capabilities here. WebdriverIO can run multiple capabilities at the same


    // time. Depending on the number of capabilities, WebdriverIO launches several test


    // sessions. Within your capabilities you can overwrite the spec and exclude options in


    // order to group specific specs to a specific capability.


    //


    // First, you can define how many instances should be started at the same time. Let's


    // say you have 3 different capabilities (Chrome, Firefox, and Safari) and you have


    // set maxInstances to 1; wdio will spawn 3 processes. Therefore, if you have 10 spec


    // files and you set maxInstances to 10, all spec files will get tested at the same time


    // and 30 processes will get spawned. The property handles how many capabilities


    // from the same test should run tests.


    //


    maxInstances: 10,


    //


    // If you have trouble getting all important capabilities together, check out the


    // Sauce Labs platform configurator - a great tool to configure your capabilities:


 


    //


    capabilities: [


        {


            // maxInstances can get overwritten per capability. So if you have an in-house Selenium


            // grid with only 5 firefox instance available you can make sure that not more than


            // 5 instance gets started at a time.


             maxInstances: 1,


            browserName: "chrome",


            chromeOptions: {


                args: ["--start-maximized", "--start-fullscreen",
                    // '--test-type', 'show-fps-counter=true', '--web-security=no spec.js', '--use-fake-device-for-media-stream', '--use-fake-ui-for-media-stream'
                ],


            },


             //seleniumProtocol: "WebDriver",


        },


 


        // {


        //     maxInstances: 1,


        //     browserName: "firefox",


        //     acceptInsecureCerts: true,


        // },


     ],


 
.............................

 


    // Gets executed after all workers got shut down and the process is about to exit. It is not


    // possible to defer the end of the process using a promise.


//     onComplete: function(exitCode) {


//     }


};

and package.json

Code:
dependencies": {
    "chai": "3.5.0",
    "chai-as-promised": "6.0.0",
    "chai-string": "1.3.0",
    "chai-subset": "1.5.0",
    "chai-things": "0.2.0",
    "jsonfile": "3.0.0",
    "moment": "2.18.1",
    "node-gyp": "3.6.1",
    "node-ninja": "1.0.2",
    "node-uuid": "1.4.8",
    "webdriverio": "4.8.0"
  },
  "peerDependencies": {
    "mocha": "^3"
  },
  "devDependencies": {
    "babel-cli": "6.24.1",
    "babel-core": "6.24.1",

    "babel-plugin-transform-object-rest-spread": "6.23.0",
    "babel-plugin-transform-runtime": "6.23.0",
    "babel-preset-es2015": "6.24.1",
    "babel-register": "6.24.1",
    "chromedriver": "2.29.0",
    "cross-env": "4.0.0",
    "eslint": "^3.19.0",
    "eslint-config-airbnb": "15.0.1",
    "eslint-plugin-import": "2.2.0",
    "eslint-plugin-jsx-a11y": "^5.0.1",
    "eslint-plugin-react": "7.0.0",
    "eslint-plugin-webdriverio": "1.0.1",
    "express": "4.15.2",
    "geckodriver": "1.6.1",
    "marked": "0.3.6",
    "marked-terminal": "2.0.0",
    "mocha": "3.3.0",
    "mocha-babel": "3.0.3",
    "mocha-junit-reporter": "1.13.0",
    "mocha-parallel-tests": "1.2.9",
    "mocha-prepare": "0.0.1",
    "mocha-traceur": "2.1.0",
    "progress": "2.0.0",
    "request": "2.81.0",
    "selenium-standalone": "6.4.1",
    "supertest": "3.0.0",
    "tedious": "2.0.0",
    "tedious-connection-pool": "1.0.5",
    "uuid": "3.0.1",
    "wdio-allure-reporter": "0.1.2",
    "wdio-browserstack-service": "0.1.4",
    "wdio-concise-reporter": "0.1.2",
    "wdio-dot-reporter": "0.0.8",
    "wdio-firefox-profile-service": "0.0.3",
    "wdio-jasmine-framework": "0.3.1",
    "wdio-json-reporter": "0.2.1",
    "wdio-junit-reporter": "0.3.0",
    "wdio-mocha-framework": "0.5.10",
    "wdio-phantomjs-service": "0.2.2",
    "wdio-sauce-service": "0.4.0",
    "wdio-selenium-standalone-service": "0.0.8",
    "wdio-spec-reporter": "0.1.0"



I made also uncomment and ran selenium standalone not from CMD

I ran also CMD terminal as "administrator" to run a test

Command for running tests: npm run name_of_test

another person have the same files the same versions and it works..so strange...for me..and also windows 10, 64bit etc.

in TASK MANAGER (window) after running tests I can see that chromedriver.exe is not running

i do not have idea what could help now:(
Back to top
Permissions in this forum:
You cannot reply to topics in this forum