Hi, I'm getting the same issue.

OS: DockerImage (Ubuntu)
Chrome: 59.0.3071.86
Chromedriver: 2.29.461571
Protractor: 5.1.2
Angular: 4.1.2

protractor.conf.js:

exports.config = {
    allScriptsTimeout: 11000,
    specs: [
        'e2e/**/*.feature'
    ],
    capabilities: {
        'browserName': 'chrome',
        chromeOptions: {
            args: ["--headless", "--disable-gpu", "--window-size=800x600"]
        }
    },
    directConnect: true,
    baseUrl: 'http://localhost:4200/',
    framework: 'custom',
    frameworkPath: require.resolve('protractor-cucumber-framework'),
    cucumberOpts: {
        require: 'e2e/**/*.steps.ts',
        tags: '@integration',
        format: ['pretty', 'json:' + testResultsJsonFile]
    },
    beforeLaunch: function () {
        require('ts-node').register({
            project: 'e2e'
        });
        fs.existsSync(testResultsFolder) || fs.mkdirSync(testResultsFolder);
    },
    useAllAngular2AppRoots: true
};


Stacktrace:

17:26:58] I/launcher - Running 1 instances of WebDriver
[17:26:58] I/direct - Using ChromeDriver directly...
[17:27:58] E/launcher - unknown error: Chrome failed to start: crashed
  (Driver info: chromedriver=2.29.461571 
(8a88bbe0775e2a23afda0ceaf2ef7ee74e822cc5),platform=Linux 4.9.27-moby 
x86_64)
[17:27:58] E/launcher - WebDriverError: unknown error: Chrome failed to 
start: crashed
  (Driver info: chromedriver=2.29.461571 
(8a88bbe0775e2a23afda0ceaf2ef7ee74e822cc5),platform=Linux 4.9.27-moby 
x86_64)
    at Object.checkLegacyResponse 
(/tmp/app/node_modules/selenium-webdriver/lib/error.js:505:15)
    at parseHttpResponse 
(/tmp/app/node_modules/selenium-webdriver/lib/http.js:509:13)
    at doSend.then.response 
(/tmp/app/node_modules/selenium-webdriver/lib/http.js:440:13)
    at process._tickCallback (internal/process/next_tick.js:109:7)
From: Task: WebDriver.createSession()
    at Function.createSession 
(/tmp/app/node_modules/selenium-webdriver/lib/webdriver.js:777:24)
    at Function.createSession 
(/tmp/app/node_modules/selenium-webdriver/chrome.js:709:29)
    at Direct.getNewDriver 
(/tmp/app/node_modules/protractor/lib/driverProviders/direct.ts:90:25)
    at Runner.createBrowser 
(/tmp/app/node_modules/protractor/lib/runner.ts:225:39)
    at q.then.then (/tmp/app/node_modules/protractor/lib/runner.ts:391:27)
    at _fulfilled 
(/tmp/app/node_modules/protractor/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done 
(/tmp/app/node_modules/protractor/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch 
(/tmp/app/node_modules/protractor/node_modules/q/q.js:796:13)
    at /tmp/app/node_modules/protractor/node_modules/q/q.js:556:49
    at runSingle 
(/tmp/app/node_modules/protractor/node_modules/q/q.js:137:13)
[17:27:58] E/launcher - Process exited with error code 199



On Monday, March 27, 2017 at 1:25:12 PM UTC+2, Naina Verma wrote:
>
> Hi ,
>
> Am trying to run integration tests inside docker container using Headless 
> chrome browser 
>
> and getting this error 
>  
>
>
> [10:05:40] E/runner - Unable to start a WebDriver session.
> [10:05:40] E/launcher - Error: WebDriverError: no such session
>   (Driver info: chromedriver=2.28.455506 
> (18f6627e265f442aeec9b6661a49fe819aeeea1f),platform=Linux 
> 4.8.13-100.fc23.x86_64 x86_64) (WARNING: The server did not provide any 
> stacktrace information)
> Command duration or timeout: 10 milliseconds
> Build info: version: '3.3.1', revision: '5234b32', time: '2017-03-10 
> 09:04:52 -0800'
> System info: host: 'cb2ff2b4a7af', ip: '172.17.0.4', os.name: 'Linux', 
> os.arch: 'amd64', os.version: '4.8.13-100.fc23.x86_64', java.version: 
> '1.8.0_121'
> Driver info: org.openqa.selenium.chrome.ChromeDriver
> Capabilities [{message=unknown error: Chrome failed to start: crashed
>   (Driver info: chromedriver=2.28.455506 
> (18f6627e265f442aeec9b6661a49fe819aeeea1f),platform=Linux 
> 4.8.13-100.fc23.x86_64 x86_64), platform=ANY}]
> Session ID: d8efce645740f1d6952360630f93c8d2
>     at WebDriverError 
> (/home/fabric8/fabric8-planner/node_modules/selenium-webdriver/lib/error.js:27:5)
>     at Object.checkLegacyResponse 
> (/home/fabric8/fabric8-planner/node_modules/selenium-webdriver/lib/error.js:505:15)
>     at parseHttpResponse 
> (/home/fabric8/fabric8-planner/node_modules/selenium-webdriver/lib/http.js:509:13)
>     at doSend.then.response 
> (/home/fabric8/fabric8-planner/node_modules/selenium-webdriver/lib/http.js:440:13)
>     at process._tickCallback (internal/process/next_tick.js:103:7)
> From: Task: WebDriver.manage().timeouts().setScriptTimeout(11000)
>     at thenableWebDriverProxy.schedule 
> (/home/fabric8/fabric8-planner/node_modules/selenium-webdriver/lib/webdriver.js:816:17)
>     at Timeouts._scheduleCommand 
> (/home/fabric8/fabric8-planner/node_modules/selenium-webdriver/lib/webdriver.js:1500:25)
>     at Timeouts.setScriptTimeout 
> (/home/fabric8/fabric8-planner/node_modules/selenium-webdriver/lib/webdriver.js:1483:17)
>     at browser_.ready.browser_.ready.then.then 
> (/home/fabric8/fabric8-planner/node_modules/protractor/lib/runner.ts:281:49)
>     at ManagedPromise.invokeCallback_ 
> (/home/fabric8/fabric8-planner/node_modules/selenium-webdriver/lib/promise.js:1366:14)
>     at TaskQueue.execute_ 
> (/home/fabric8/fabric8-planner/node_modules/selenium-webdriver/lib/promise.js:2970:14)
>     at TaskQueue.executeNext_ 
> (/home/fabric8/fabric8-planner/node_modules/selenium-webdriver/lib/promise.js:2953:27)
>     at asyncRun 
> (/home/fabric8/fabric8-planner/node_modules/selenium-webdriver/lib/promise.js:2813:27)
>     at 
> /home/fabric8/fabric8-planner/node_modules/selenium-webdriver/lib/promise.js:676:7
>     at process._tickCallback (internal/process/next_tick.js:103:7)
> [10:05:40] E/launcher - Process exited with error code 100
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to