New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

problem testing e2e in docker image #114

Closed
geoHeil opened this Issue Jul 3, 2016 · 24 comments

Comments

Projects
None yet
2 participants
@geoHeil

geoHeil commented Jul 3, 2016

Hi, I have problems running the e2e tests in the following docker image: https://gist.github.com/geoHeil/48cd94bf4d748fd8fd6d25de4c272157

Chrome seems to be unreachable, even though chromium is installed:

WebDriverError: chrome not reachable
  (Driver info: chromedriver=2.21.371461 (633e689b520b25f3e264a2ede6b74ccc23cb636a),platform=Linux 4.4.14-moby x86_64)
    at WebDriverError (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:27:10)
    at Object.checkLegacyResponse (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:580:13)
    at /home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:64:13
    at Promise.invokeCallback_ (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:1329:14)
    at TaskQueue.execute_ (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2790:14)
    at TaskQueue.executeNext_ (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2773:21)
    at /home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2652:27
    at /home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:639:7
    at process._tickCallback (node.js:369:9)
From: Task: WebDriver.createSession()
    at acquireSession (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:62:22)
    at Function.createSession (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:295:12)
    at Driver (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/chrome.js:778:38)
    at Direct.getNewDriver (/home/jenkins/clicker/node_modules/protractor/built/driverProviders/direct.js:65:26)
    at Runner.createBrowser (/home/jenkins/clicker/node_modules/protractor/built/runner.js:182:43)
    at /home/jenkins/clicker/node_modules/protractor/built/runner.js:255:30
    at _fulfilled (/home/jenkins/clicker/node_modules/protractor/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/home/jenkins/clicker/node_modules/protractor/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/home/jenkins/clicker/node_modules/protractor/node_modules/q/q.js:796:13)
    at /home/jenkins/clicker/node_modules/protractor/node_modules/q/q.js:556:49
@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 3, 2016

Owner

I've not been able to get it working with Chromium. I use chrome locally as
well as on Travis.

On 3 Jul 2016 23:40, "geoHeil" notifications@github.com wrote:

Hi, I have problems running the e2e tests in the following docker image:
https://gist.github.com/geoHeil/48cd94bf4d748fd8fd6d25de4c272157

Chrome seems to be unreachable, even though chromium is installed:

WebDriverError: chrome not reachable
(Driver info: chromedriver=2.21.371461 (633e689b520b25f3e264a2ede6b74ccc23cb636a),platform=Linux 4.4.14-moby x86_64)
at WebDriverError (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:27:10)
at Object.checkLegacyResponse (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:580:13)
at /home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:64:13
at Promise.invokeCallback_ (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:1329:14)
at TaskQueue.execute_ (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2790:14)
at TaskQueue.executeNext_ (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2773:21)
at /home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2652:27
at /home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:639:7
at process._tickCallback (node.js:369:9)
From: Task: WebDriver.createSession()
at acquireSession (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:62:22)
at Function.createSession (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:295:12)
at Driver (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/chrome.js:778:38)
at Direct.getNewDriver (/home/jenkins/clicker/node_modules/protractor/built/driverProviders/direct.js:65:26)
at Runner.createBrowser (/home/jenkins/clicker/node_modules/protractor/built/runner.js:182:43)
at /home/jenkins/clicker/node_modules/protractor/built/runner.js:255:30
at _fulfilled (/home/jenkins/clicker/node_modules/protractor/node_modules/q/q.js:834:54)
at self.promiseDispatch.done (/home/jenkins/clicker/node_modules/protractor/node_modules/q/q.js:863:30)
at Promise.promise.promiseDispatch (/home/jenkins/clicker/node_modules/protractor/node_modules/q/q.js:796:13)
at /home/jenkins/clicker/node_modules/protractor/node_modules/q/q.js:556:49


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#114, or mute the thread
https://github.com/notifications/unsubscribe/AG5tSJ1Fd01vNX2gxQMB1ugfnUV88qg3ks5qR7vhgaJpZM4JD3xQ
.

Owner

lathonez commented Jul 3, 2016

I've not been able to get it working with Chromium. I use chrome locally as
well as on Travis.

On 3 Jul 2016 23:40, "geoHeil" notifications@github.com wrote:

Hi, I have problems running the e2e tests in the following docker image:
https://gist.github.com/geoHeil/48cd94bf4d748fd8fd6d25de4c272157

Chrome seems to be unreachable, even though chromium is installed:

WebDriverError: chrome not reachable
(Driver info: chromedriver=2.21.371461 (633e689b520b25f3e264a2ede6b74ccc23cb636a),platform=Linux 4.4.14-moby x86_64)
at WebDriverError (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:27:10)
at Object.checkLegacyResponse (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:580:13)
at /home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:64:13
at Promise.invokeCallback_ (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:1329:14)
at TaskQueue.execute_ (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2790:14)
at TaskQueue.executeNext_ (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2773:21)
at /home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2652:27
at /home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:639:7
at process._tickCallback (node.js:369:9)
From: Task: WebDriver.createSession()
at acquireSession (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:62:22)
at Function.createSession (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:295:12)
at Driver (/home/jenkins/clicker/node_modules/protractor/node_modules/selenium-webdriver/chrome.js:778:38)
at Direct.getNewDriver (/home/jenkins/clicker/node_modules/protractor/built/driverProviders/direct.js:65:26)
at Runner.createBrowser (/home/jenkins/clicker/node_modules/protractor/built/runner.js:182:43)
at /home/jenkins/clicker/node_modules/protractor/built/runner.js:255:30
at _fulfilled (/home/jenkins/clicker/node_modules/protractor/node_modules/q/q.js:834:54)
at self.promiseDispatch.done (/home/jenkins/clicker/node_modules/protractor/node_modules/q/q.js:863:30)
at Promise.promise.promiseDispatch (/home/jenkins/clicker/node_modules/protractor/node_modules/q/q.js:796:13)
at /home/jenkins/clicker/node_modules/protractor/node_modules/q/q.js:556:49


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#114, or mute the thread
https://github.com/notifications/unsubscribe/AG5tSJ1Fd01vNX2gxQMB1ugfnUV88qg3ks5qR7vhgaJpZM4JD3xQ
.

@geoHeil

This comment has been minimized.

Show comment
Hide comment
@geoHeil

geoHeil Jul 3, 2016

I updated the Dockerfile to use chrome https://gist.github.com/geoHeil/48cd94bf4d748fd8fd6d25de4c272157 but still keep getting this error.

geoHeil commented Jul 3, 2016

I updated the Dockerfile to use chrome https://gist.github.com/geoHeil/48cd94bf4d748fd8fd6d25de4c272157 but still keep getting this error.

@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 4, 2016

Owner

I can't build using that dockerfile, which is relies on files that exist on your system.

In particular I'm getting:

Step 10 : COPY /files/authorized_keys /home/jenkins/.ssh/authorized_keys
lstat files/authorized_keys: no such file or directory

But I can see plenty of steps later on in the file that should also fail.

Have you looked at our travis.yml?

Owner

lathonez commented Jul 4, 2016

I can't build using that dockerfile, which is relies on files that exist on your system.

In particular I'm getting:

Step 10 : COPY /files/authorized_keys /home/jenkins/.ssh/authorized_keys
lstat files/authorized_keys: no such file or directory

But I can see plenty of steps later on in the file that should also fail.

Have you looked at our travis.yml?

@geoHeil

This comment has been minimized.

Show comment
Hide comment
@geoHeil

geoHeil Jul 4, 2016

Which steps are you referring to? They all do work. For the keys, you can use any random key.

Currently, I try to use https://github.com/jciolek/docker-protractor-headless respectively http://tobyho.com/2015/01/09/headless-browser-testing-xvfb/

geoHeil commented Jul 4, 2016

Which steps are you referring to? They all do work. For the keys, you can use any random key.

Currently, I try to use https://github.com/jciolek/docker-protractor-headless respectively http://tobyho.com/2015/01/09/headless-browser-testing-xvfb/

@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 4, 2016

Owner

Sorry if I was unclear.

I ran docker build -t clicker_114 . in an empty directory containing your dockerfile

and got the following error:

Step 10 : COPY /files/authorized_keys /home/jenkins/.ssh/authorized_keys
lstat files/authorized_keys: no such file or directory

I presume any steps referencing /files would fail:

x220:~/code/clicker_114$ grep files Dockerfile 
COPY /files/authorized_keys /home/jenkins/.ssh/authorized_keys
COPY /files/resolv.conf /etc/resolv.conf
COPY /files/installAndroid.sh /installAndroid.sh

Could you provide command(s) I can run to generate the docker image you refer to, or (preferably) make an image available that I can pull down.

Currently, I try to use https://github.com/jciolek/docker-protractor-headless respectively http://tobyho.com/2015/01/09/headless-browser-testing-xvfb/

I am unclear whether this means you have solved your problem or not?

Owner

lathonez commented Jul 4, 2016

Sorry if I was unclear.

I ran docker build -t clicker_114 . in an empty directory containing your dockerfile

and got the following error:

Step 10 : COPY /files/authorized_keys /home/jenkins/.ssh/authorized_keys
lstat files/authorized_keys: no such file or directory

I presume any steps referencing /files would fail:

x220:~/code/clicker_114$ grep files Dockerfile 
COPY /files/authorized_keys /home/jenkins/.ssh/authorized_keys
COPY /files/resolv.conf /etc/resolv.conf
COPY /files/installAndroid.sh /installAndroid.sh

Could you provide command(s) I can run to generate the docker image you refer to, or (preferably) make an image available that I can pull down.

Currently, I try to use https://github.com/jciolek/docker-protractor-headless respectively http://tobyho.com/2015/01/09/headless-browser-testing-xvfb/

I am unclear whether this means you have solved your problem or not?

@geoHeil

This comment has been minimized.

Show comment
Hide comment
@geoHeil

geoHeil Jul 4, 2016

The problem is not solved yet. I will update the dockerfile for you late afternoon. Thanks a lot for the support.

geoHeil commented Jul 4, 2016

The problem is not solved yet. I will update the dockerfile for you late afternoon. Thanks a lot for the support.

@geoHeil

This comment has been minimized.

Show comment
Hide comment
@geoHeil

geoHeil Jul 4, 2016

I updated the dockerfile here: https://gist.github.com/geoHeil/48cd94bf4d748fd8fd6d25de4c272157
a npm test should run just fine,
a npm run e2e should unfortunately fail.

geoHeil commented Jul 4, 2016

I updated the dockerfile here: https://gist.github.com/geoHeil/48cd94bf4d748fd8fd6d25de4c272157
a npm test should run just fine,
a npm run e2e should unfortunately fail.

@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 5, 2016

Owner

Everything is owned by root so I can't run any tests:

jenkins@1bdea5fd764a:~/clicker$ ls -ltr
total 60
drwxr-xr-x  3 root root    38 Jul  5 08:19 www
-rw-r--r--  1 root root   403 Jul  5 08:19 typings.json
-rw-r--r--  1 root root  2550 Jul  5 08:19 tslint.json
-rw-r--r--  1 root root   321 Jul  5 08:19 tsconfig.json
drwxr-xr-x  3 root root   150 Jul  5 08:19 test
drwxr-xr-x  4 root root    66 Jul  5 08:19 resources
-rw-r--r--  1 root root  2418 Jul  5 08:19 package.json
-rw-r--r--  1 root root    48 Jul  5 08:19 ionic.project
-rw-r--r--  1 root root    76 Jul  5 08:19 ionic.config.json
drwxr-xr-x  3 root root    44 Jul  5 08:19 hooks
-rw-r--r--  1 root root  2264 Jul  5 08:19 gulpfile.js
-rw-r--r--  1 root root  1319 Jul  5 08:19 config.xml
drwxr-xr-x  7 root root   147 Jul  5 08:19 app
-rw-r--r--  1 root root  3968 Jul  5 08:19 README.md
-rw-r--r--  1 root root  1078 Jul  5 08:19 LICENSE
-rw-r--r--  1 root root 13345 Jul  5 08:19 CHANGELOG.md
drwxr-xr-x 44 root root  4096 Jul  5 08:20 node_modules
drwxr-xr-x  3 root root    39 Jul  5 08:23 typings
jenkins@1bdea5fd764a:~/clicker$ 
jenkins@1bdea5fd764a:~/clicker$ npm test

> clicker@1.8.1 test /home/jenkins/clicker
> gulp --gulpfile test/gulpfile.ts --cwd ./ unit-test

[08:39:39] Requiring external module ts-node/register
[08:39:42] Using gulpfile ~/clicker/test/gulpfile.ts
[08:39:42] Starting 'unit-test'...
[08:39:42] Starting 'lint'...
[08:39:42] Starting 'html'...
[08:39:42] 'html' errored after 228 ms
[08:39:42] Error: EACCES: permission denied, mkdir '/home/jenkins/clicker/www/build'
    at Error (native)
[08:39:42] 'unit-test' errored after 385 ms
[08:39:42] Error in plugin 'run-sequence(html)'
Message:
    html stream
[08:39:43] Finished 'lint' after 1.37 s
npm ERR! Test failed.  See above for more details.

what's the sudo password for jenkins / how can I connect as root?

Owner

lathonez commented Jul 5, 2016

Everything is owned by root so I can't run any tests:

jenkins@1bdea5fd764a:~/clicker$ ls -ltr
total 60
drwxr-xr-x  3 root root    38 Jul  5 08:19 www
-rw-r--r--  1 root root   403 Jul  5 08:19 typings.json
-rw-r--r--  1 root root  2550 Jul  5 08:19 tslint.json
-rw-r--r--  1 root root   321 Jul  5 08:19 tsconfig.json
drwxr-xr-x  3 root root   150 Jul  5 08:19 test
drwxr-xr-x  4 root root    66 Jul  5 08:19 resources
-rw-r--r--  1 root root  2418 Jul  5 08:19 package.json
-rw-r--r--  1 root root    48 Jul  5 08:19 ionic.project
-rw-r--r--  1 root root    76 Jul  5 08:19 ionic.config.json
drwxr-xr-x  3 root root    44 Jul  5 08:19 hooks
-rw-r--r--  1 root root  2264 Jul  5 08:19 gulpfile.js
-rw-r--r--  1 root root  1319 Jul  5 08:19 config.xml
drwxr-xr-x  7 root root   147 Jul  5 08:19 app
-rw-r--r--  1 root root  3968 Jul  5 08:19 README.md
-rw-r--r--  1 root root  1078 Jul  5 08:19 LICENSE
-rw-r--r--  1 root root 13345 Jul  5 08:19 CHANGELOG.md
drwxr-xr-x 44 root root  4096 Jul  5 08:20 node_modules
drwxr-xr-x  3 root root    39 Jul  5 08:23 typings
jenkins@1bdea5fd764a:~/clicker$ 
jenkins@1bdea5fd764a:~/clicker$ npm test

> clicker@1.8.1 test /home/jenkins/clicker
> gulp --gulpfile test/gulpfile.ts --cwd ./ unit-test

[08:39:39] Requiring external module ts-node/register
[08:39:42] Using gulpfile ~/clicker/test/gulpfile.ts
[08:39:42] Starting 'unit-test'...
[08:39:42] Starting 'lint'...
[08:39:42] Starting 'html'...
[08:39:42] 'html' errored after 228 ms
[08:39:42] Error: EACCES: permission denied, mkdir '/home/jenkins/clicker/www/build'
    at Error (native)
[08:39:42] 'unit-test' errored after 385 ms
[08:39:42] Error in plugin 'run-sequence(html)'
Message:
    html stream
[08:39:43] Finished 'lint' after 1.37 s
npm ERR! Test failed.  See above for more details.

what's the sudo password for jenkins / how can I connect as root?

@geoHeil

This comment has been minimized.

Show comment
Hide comment
@geoHeil

geoHeil Jul 5, 2016

A bad quick- fix is to just remove the last USER jenkins statement.
A cleaner fix is to re-checkout the repository into /home/jenkins with the default jenkins user

geoHeil commented Jul 5, 2016

A bad quick- fix is to just remove the last USER jenkins statement.
A cleaner fix is to re-checkout the repository into /home/jenkins with the default jenkins user

@geoHeil

This comment has been minimized.

Show comment
Hide comment
@geoHeil

geoHeil Jul 5, 2016

I updated the dockerfile.
Chrome does not seem to be available. However directly starting chrome results in this strange error: xvfb-run google-chrome google.com
1__jenkins_68dd4423752e___var__docker_

geoHeil commented Jul 5, 2016

I updated the dockerfile.
Chrome does not seem to be available. However directly starting chrome results in this strange error: xvfb-run google-chrome google.com
1__jenkins_68dd4423752e___var__docker_

@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 5, 2016

Owner

A cleaner fix is to re-checkout the repository into /home/jenkins with the default jenkins user

Sorry, should have figured that one out. Lots going on. I'm with you now.

Yeah I figure it's something to do with the xdisplay.

Travis is headless and we do

export DISPLAY=:99.0
sh -e /etc/init.d/xvfb start

before the tests (why I was referencing it before)

Owner

lathonez commented Jul 5, 2016

A cleaner fix is to re-checkout the repository into /home/jenkins with the default jenkins user

Sorry, should have figured that one out. Lots going on. I'm with you now.

Yeah I figure it's something to do with the xdisplay.

Travis is headless and we do

export DISPLAY=:99.0
sh -e /etc/init.d/xvfb start

before the tests (why I was referencing it before)

@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 5, 2016

Owner

@geoHeil how can I get root in this image?

EDIT: rebuilding minus the last line as suggested.

Owner

lathonez commented Jul 5, 2016

@geoHeil how can I get root in this image?

EDIT: rebuilding minus the last line as suggested.

@geoHeil

This comment has been minimized.

Show comment
Hide comment
@geoHeil

geoHeil Jul 5, 2016

You can change the User in the dockerfile via USER root and then re-build the image.
In case you just add it at the bottom, this will be very quick due to dockers cache.

geoHeil commented Jul 5, 2016

You can change the User in the dockerfile via USER root and then re-build the image.
In case you just add it at the bottom, this will be very quick due to dockers cache.

@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 5, 2016

Owner

Finally got it working, though not in your image at the moment.

I'm running arch which has a ton of problems with google chrome on the standard kernel: ref jessfraz/dockerfiles#65 and has caused me no end of issues.

I'm hoping the key is:

"e2e": "gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js"

in package.json

This is on my dev docker image:

DEV:~/clicker$ npm run e2e

> clicker@1.8.1 e2e /home/wherewolf/clicker
> gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js

[13:59:39] Requiring external module ts-node/register
[13:59:41] Using gulpfile ~/clicker/test/gulpfile.ts
[13:59:41] Starting 'clean-test'...
Deleted /home/wherewolf/clicker/www/build/test
[13:59:41] Finished 'clean-test' after 11 ms
[13:59:41] Starting 'build-e2e'...
[13:59:42] Finished 'build-e2e' after 1.47 s
[13:59:43] I/direct - Using ChromeDriver directly...
[13:59:43] I/launcher - Running 1 instances of WebDriver
Spec started
Started

  ClickerApp
    ✓ should have a title
.    ✓ should have <nav>
.    ✓ should have correct nav text for Home
.    ✓ has a menu button that displays the left menu
.    ✓ the left menu has a link with title Clickers
.    ✓ the left menu has a link with title Goodbye Ionic
.
  ClickerList
    ✓ should switch into clickers page from menu
.    ✓ has an input box for new Clickers
.    ✗ should add a Clicker
      - Expected 'test clicker one (0)' to equal 'TEST CLICKER ONE (0)'.
F    ✗ should click a Clicker
      - Expected 'test clicker one (1)' to equal 'TEST CLICKER ONE (1)'.
F    ✓ should delete a Clicker
.
  Page2
    ✓ should have correct text when Goodbye Ionic is selected
.
**************************************************
*                    Failures                    *
**************************************************

1) ClickerList should add a Clicker
  - Expected 'test clicker one (0)' to equal 'TEST CLICKER ONE (0)'.

2) ClickerList should click a Clicker
  - Expected 'test clicker one (1)' to equal 'TEST CLICKER ONE (1)'.

Executed 12 of 12 specs (2 FAILED) in 1 min 28 secs.


Failures:
1) ClickerList should add a Clicker
  Message:
    Expected 'test clicker one (0)' to equal 'TEST CLICKER ONE (0)'.
  Stack:
    Error: Failed expectation
        at Object.<anonymous> (/home/wherewolf/clicker/www/build/test/pages/clickerList/clickerList.e2e.js:21:40)
        at /home/wherewolf/clicker/node_modules/jasminewd2/index.js:96:23
        at new Promise (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:1043:7)
        at controlFlowExecute (/home/wherewolf/clicker/node_modules/jasminewd2/index.js:82:18)
        at TaskQueue.execute_ (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:2790:14)
        at TaskQueue.executeNext_ (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:2773:21)
        at asyncRun (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:2697:25)
        at /home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:639:7
        at process._tickCallback (internal/process/next_tick.js:103:7)

2) ClickerList should click a Clicker
  Message:
    Expected 'test clicker one (1)' to equal 'TEST CLICKER ONE (1)'.
  Stack:
    Error: Failed expectation
        at Object.<anonymous> (/home/wherewolf/clicker/www/build/test/pages/clickerList/clickerList.e2e.js:26:40)
        at /home/wherewolf/clicker/node_modules/jasminewd2/index.js:96:23
        at new Promise (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:1043:7)
        at controlFlowExecute (/home/wherewolf/clicker/node_modules/jasminewd2/index.js:82:18)
        at TaskQueue.execute_ (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:2790:14)
        at TaskQueue.executeNext_ (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:2773:21)
        at asyncRun (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:2697:25)
        at /home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:639:7
        at process._tickCallback (internal/process/next_tick.js:103:7)

12 specs, 2 failures
Finished in 87.908 seconds
[14:01:11] I/launcher - 0 instance(s) of WebDriver still running
[14:01:11] I/launcher - chrome #01 failed 2 test(s)
[14:01:11] I/launcher - overall: 2 failed spec(s)
[14:01:11] E/launcher - Process exited with error code 1

npm ERR! Linux 4.6.3-1-ARCH
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "e2e"
npm ERR! node v6.2.2
npm ERR! npm  v3.9.5
npm ERR! code ELIFECYCLE
npm ERR! clicker@1.8.1 e2e: `gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the clicker@1.8.1 e2e script 'gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the clicker package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs clicker
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls clicker
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/wherewolf/clicker/npm-debug.log
Owner

lathonez commented Jul 5, 2016

Finally got it working, though not in your image at the moment.

I'm running arch which has a ton of problems with google chrome on the standard kernel: ref jessfraz/dockerfiles#65 and has caused me no end of issues.

I'm hoping the key is:

"e2e": "gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js"

in package.json

This is on my dev docker image:

DEV:~/clicker$ npm run e2e

> clicker@1.8.1 e2e /home/wherewolf/clicker
> gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js

[13:59:39] Requiring external module ts-node/register
[13:59:41] Using gulpfile ~/clicker/test/gulpfile.ts
[13:59:41] Starting 'clean-test'...
Deleted /home/wherewolf/clicker/www/build/test
[13:59:41] Finished 'clean-test' after 11 ms
[13:59:41] Starting 'build-e2e'...
[13:59:42] Finished 'build-e2e' after 1.47 s
[13:59:43] I/direct - Using ChromeDriver directly...
[13:59:43] I/launcher - Running 1 instances of WebDriver
Spec started
Started

  ClickerApp
    ✓ should have a title
.    ✓ should have <nav>
.    ✓ should have correct nav text for Home
.    ✓ has a menu button that displays the left menu
.    ✓ the left menu has a link with title Clickers
.    ✓ the left menu has a link with title Goodbye Ionic
.
  ClickerList
    ✓ should switch into clickers page from menu
.    ✓ has an input box for new Clickers
.    ✗ should add a Clicker
      - Expected 'test clicker one (0)' to equal 'TEST CLICKER ONE (0)'.
F    ✗ should click a Clicker
      - Expected 'test clicker one (1)' to equal 'TEST CLICKER ONE (1)'.
F    ✓ should delete a Clicker
.
  Page2
    ✓ should have correct text when Goodbye Ionic is selected
.
**************************************************
*                    Failures                    *
**************************************************

1) ClickerList should add a Clicker
  - Expected 'test clicker one (0)' to equal 'TEST CLICKER ONE (0)'.

2) ClickerList should click a Clicker
  - Expected 'test clicker one (1)' to equal 'TEST CLICKER ONE (1)'.

Executed 12 of 12 specs (2 FAILED) in 1 min 28 secs.


Failures:
1) ClickerList should add a Clicker
  Message:
    Expected 'test clicker one (0)' to equal 'TEST CLICKER ONE (0)'.
  Stack:
    Error: Failed expectation
        at Object.<anonymous> (/home/wherewolf/clicker/www/build/test/pages/clickerList/clickerList.e2e.js:21:40)
        at /home/wherewolf/clicker/node_modules/jasminewd2/index.js:96:23
        at new Promise (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:1043:7)
        at controlFlowExecute (/home/wherewolf/clicker/node_modules/jasminewd2/index.js:82:18)
        at TaskQueue.execute_ (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:2790:14)
        at TaskQueue.executeNext_ (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:2773:21)
        at asyncRun (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:2697:25)
        at /home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:639:7
        at process._tickCallback (internal/process/next_tick.js:103:7)

2) ClickerList should click a Clicker
  Message:
    Expected 'test clicker one (1)' to equal 'TEST CLICKER ONE (1)'.
  Stack:
    Error: Failed expectation
        at Object.<anonymous> (/home/wherewolf/clicker/www/build/test/pages/clickerList/clickerList.e2e.js:26:40)
        at /home/wherewolf/clicker/node_modules/jasminewd2/index.js:96:23
        at new Promise (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:1043:7)
        at controlFlowExecute (/home/wherewolf/clicker/node_modules/jasminewd2/index.js:82:18)
        at TaskQueue.execute_ (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:2790:14)
        at TaskQueue.executeNext_ (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:2773:21)
        at asyncRun (/home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:2697:25)
        at /home/wherewolf/clicker/node_modules/selenium-webdriver/lib/promise.js:639:7
        at process._tickCallback (internal/process/next_tick.js:103:7)

12 specs, 2 failures
Finished in 87.908 seconds
[14:01:11] I/launcher - 0 instance(s) of WebDriver still running
[14:01:11] I/launcher - chrome #01 failed 2 test(s)
[14:01:11] I/launcher - overall: 2 failed spec(s)
[14:01:11] E/launcher - Process exited with error code 1

npm ERR! Linux 4.6.3-1-ARCH
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "e2e"
npm ERR! node v6.2.2
npm ERR! npm  v3.9.5
npm ERR! code ELIFECYCLE
npm ERR! clicker@1.8.1 e2e: `gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the clicker@1.8.1 e2e script 'gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the clicker package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs clicker
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls clicker
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/wherewolf/clicker/npm-debug.log
@geoHeil

This comment has been minimized.

Show comment
Hide comment
@geoHeil

geoHeil Jul 5, 2016

Great. So far I only got it this problem: Client failed to connect to the D-BUS daemon and found this posting http://stackoverflow.com/questions/28495341/start-a-service-in-docker-container-failed-with-error-failed-to-get-d-bus-conne I will have a look at your solution.

geoHeil commented Jul 5, 2016

Great. So far I only got it this problem: Client failed to connect to the D-BUS daemon and found this posting http://stackoverflow.com/questions/28495341/start-a-service-in-docker-container-failed-with-error-failed-to-get-d-bus-conne I will have a look at your solution.

@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 5, 2016

Owner

I'm not sure how much of a problem that is. Chrome stayed up for me.

dbus seems pretty badly broken on your image.

On my image I solved the error you mention by:

apt-get install dbus-x11
service dbus start

before running chrome.. tbh I don't think it's causing a problem

Owner

lathonez commented Jul 5, 2016

I'm not sure how much of a problem that is. Chrome stayed up for me.

dbus seems pretty badly broken on your image.

On my image I solved the error you mention by:

apt-get install dbus-x11
service dbus start

before running chrome.. tbh I don't think it's causing a problem

@geoHeil

This comment has been minimized.

Show comment
Hide comment
@geoHeil

geoHeil Jul 5, 2016

could you post your image / dockerfile?

geoHeil commented Jul 5, 2016

could you post your image / dockerfile?

@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 5, 2016

Owner

Not in it's current state as it has my company's IP all over it. I ultimatley will be able to post one if necessary.

Give me a minute I'm trying to get it running on yours.

Owner

lathonez commented Jul 5, 2016

Not in it's current state as it has my company's IP all over it. I ultimatley will be able to post one if necessary.

Give me a minute I'm trying to get it running on yours.

@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 5, 2016

Owner

It works, modify your package.json:

jenkins@f007b5e7eec4:~/clicker$ git diff package.json 
diff --git a/package.json b/package.json
index 67f354a..065e5b0 100644
--- a/package.json
+++ b/package.json
@@ -61,7 +61,7 @@
   "cordovaPlatforms": [],
   "scripts": {
     "build": "gulp --gulpfile test/gulpfile.ts --cwd ./ build-app",
-    "e2e": "gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && protractor test/protractor.c
+    "e2e": "gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/pro
     "karma": "gulp --gulpfile test/gulpfile.ts --cwd ./ karma-debug",
     "postinstall": "ionic state restore && typings install && webdriver-manager update && cp te
     "start": "ionic serve",

I also had to make the following change (adding the --no-sandbox flag) to the google-chrome script in /usr/bin:

jenkins@f007b5e7eec4:/usr/bin$ diff /tmp/google-chrome google-chrome
74c74
<   exec -a "$0" "$HERE/chrome" "$@"
---
>   exec -a "$0" "$HERE/chrome" --no-sandbox "$@"

This is arch specific though as I mention above, it shouldn't affect you as you seem to be on mac.

Owner

lathonez commented Jul 5, 2016

It works, modify your package.json:

jenkins@f007b5e7eec4:~/clicker$ git diff package.json 
diff --git a/package.json b/package.json
index 67f354a..065e5b0 100644
--- a/package.json
+++ b/package.json
@@ -61,7 +61,7 @@
   "cordovaPlatforms": [],
   "scripts": {
     "build": "gulp --gulpfile test/gulpfile.ts --cwd ./ build-app",
-    "e2e": "gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && protractor test/protractor.c
+    "e2e": "gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/pro
     "karma": "gulp --gulpfile test/gulpfile.ts --cwd ./ karma-debug",
     "postinstall": "ionic state restore && typings install && webdriver-manager update && cp te
     "start": "ionic serve",

I also had to make the following change (adding the --no-sandbox flag) to the google-chrome script in /usr/bin:

jenkins@f007b5e7eec4:/usr/bin$ diff /tmp/google-chrome google-chrome
74c74
<   exec -a "$0" "$HERE/chrome" "$@"
---
>   exec -a "$0" "$HERE/chrome" --no-sandbox "$@"

This is arch specific though as I mention above, it shouldn't affect you as you seem to be on mac.

@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 5, 2016

Owner

Running on your image:

jenkins@f007b5e7eec4:~/clicker$ npm run e2e

> clicker@1.8.1 e2e /home/jenkins/clicker
> gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js

[14:14:29] Requiring external module ts-node/register
[14:14:31] Using gulpfile ~/clicker/test/gulpfile.ts
[14:14:31] Starting 'clean-test'...
Deleted /home/jenkins/clicker/www/build/test
[14:14:31] Finished 'clean-test' after 13 ms
[14:14:31] Starting 'build-e2e'...
[14:14:33] Finished 'build-e2e' after 1.99 s
[14:14:34] I/direct - Using ChromeDriver directly...
[14:14:34] I/launcher - Running 1 instances of WebDriver
Spec started
Started

  ClickerApp
    ✓ should have a title
.    ✓ should have <nav>
.    ✓ should have correct nav text for Home
.    ✓ has a menu button that displays the left menu
.    ✓ the left menu has a link with title Clickers
.    ✓ the left menu has a link with title Goodbye Ionic
.
  ClickerList
    ✓ should switch into clickers page from menu
.    ✓ has an input box for new Clickers
.    ✓ should add a Clicker
.    ✓ should click a Clicker
.    ✓ should delete a Clicker
.
  Page2
    ✓ should have correct text when Goodbye Ionic is selected
.
Executed 12 of 12 specs SUCCESS in 27 secs.



12 specs, 0 failures
Finished in 27.458 seconds
[14:15:02] I/launcher - 0 instance(s) of WebDriver still running
[14:15:02] I/launcher - chrome #01 passed
jenkins@f007b5e7eec4:~/clicker$ 
Owner

lathonez commented Jul 5, 2016

Running on your image:

jenkins@f007b5e7eec4:~/clicker$ npm run e2e

> clicker@1.8.1 e2e /home/jenkins/clicker
> gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js

[14:14:29] Requiring external module ts-node/register
[14:14:31] Using gulpfile ~/clicker/test/gulpfile.ts
[14:14:31] Starting 'clean-test'...
Deleted /home/jenkins/clicker/www/build/test
[14:14:31] Finished 'clean-test' after 13 ms
[14:14:31] Starting 'build-e2e'...
[14:14:33] Finished 'build-e2e' after 1.99 s
[14:14:34] I/direct - Using ChromeDriver directly...
[14:14:34] I/launcher - Running 1 instances of WebDriver
Spec started
Started

  ClickerApp
    ✓ should have a title
.    ✓ should have <nav>
.    ✓ should have correct nav text for Home
.    ✓ has a menu button that displays the left menu
.    ✓ the left menu has a link with title Clickers
.    ✓ the left menu has a link with title Goodbye Ionic
.
  ClickerList
    ✓ should switch into clickers page from menu
.    ✓ has an input box for new Clickers
.    ✓ should add a Clicker
.    ✓ should click a Clicker
.    ✓ should delete a Clicker
.
  Page2
    ✓ should have correct text when Goodbye Ionic is selected
.
Executed 12 of 12 specs SUCCESS in 27 secs.



12 specs, 0 failures
Finished in 27.458 seconds
[14:15:02] I/launcher - 0 instance(s) of WebDriver still running
[14:15:02] I/launcher - chrome #01 passed
jenkins@f007b5e7eec4:~/clicker$ 
@geoHeil

This comment has been minimized.

Show comment
Hide comment
@geoHeil

geoHeil Jul 5, 2016

Wow thanks a lot. But still I do not quite get it working:
after a
./node_modules/protractor/bin/webdriver-manager update because only the global driver was updated
I get the well known timeout that chrome is unreachable:

clicker@1.8.1 e2ej /home/clicker
> gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js

Finished 'clean-test' after 13 ms
[14:21:12] Starting 'build-e2e'...
[14:21:14] Finished 'build-e2e' after 1.72 s
[14:21:14] I/direct - Using ChromeDriver directly...
[14:21:14] I/launcher - Running 1 instances of WebDriver

/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:27
    super(opt_error);
         ^
WebDriverError: chrome not reachable
  (Driver info: chromedriver=2.21.371461 (633e689b520b25f3e264a2ede6b74ccc23cb636a),platform=Linux 4.4.14-moby x86_64)
    at WebDriverError (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:27:10)
    at Object.checkLegacyResponse (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:580:13)
    at /home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:64:13
    at Promise.invokeCallback_ (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:1329:14)
    at TaskQueue.execute_ (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2790:14)
    at TaskQueue.executeNext_ (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2773:21)
    at /home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2652:27
    at /home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:639:7
    at process._tickCallback (node.js:369:9)
From: Task: WebDriver.createSession()
    at acquireSession (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:62:22)
    at Function.createSession (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:295:12)
    at Driver (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/chrome.js:778:38)
    at Direct.getNewDriver (/home/clicker/node_modules/protractor/built/driverProviders/direct.js:65:26)
    at Runner.createBrowser (/home/clicker/node_modules/protractor/built/runner.js:182:43)
    at /home/clicker/node_modules/protractor/built/runner.js:255:30
    at _fulfilled (/home/clicker/node_modules/protractor/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/home/clicker/node_modules/protractor/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/home/clicker/node_modules/protractor/node_modules/q/q.js:796:13)
    at /home/clicker/node_modules/protractor/node_modules/q/q.js:556:49
[14:22:14] E/launcher - Process exited with error code 1

geoHeil commented Jul 5, 2016

Wow thanks a lot. But still I do not quite get it working:
after a
./node_modules/protractor/bin/webdriver-manager update because only the global driver was updated
I get the well known timeout that chrome is unreachable:

clicker@1.8.1 e2ej /home/clicker
> gulp --gulpfile test/gulpfile.ts --cwd ./ build-e2e && xvfb-run protractor test/protractor.conf.js

Finished 'clean-test' after 13 ms
[14:21:12] Starting 'build-e2e'...
[14:21:14] Finished 'build-e2e' after 1.72 s
[14:21:14] I/direct - Using ChromeDriver directly...
[14:21:14] I/launcher - Running 1 instances of WebDriver

/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:27
    super(opt_error);
         ^
WebDriverError: chrome not reachable
  (Driver info: chromedriver=2.21.371461 (633e689b520b25f3e264a2ede6b74ccc23cb636a),platform=Linux 4.4.14-moby x86_64)
    at WebDriverError (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:27:10)
    at Object.checkLegacyResponse (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:580:13)
    at /home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:64:13
    at Promise.invokeCallback_ (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:1329:14)
    at TaskQueue.execute_ (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2790:14)
    at TaskQueue.executeNext_ (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2773:21)
    at /home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2652:27
    at /home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:639:7
    at process._tickCallback (node.js:369:9)
From: Task: WebDriver.createSession()
    at acquireSession (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:62:22)
    at Function.createSession (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:295:12)
    at Driver (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/chrome.js:778:38)
    at Direct.getNewDriver (/home/clicker/node_modules/protractor/built/driverProviders/direct.js:65:26)
    at Runner.createBrowser (/home/clicker/node_modules/protractor/built/runner.js:182:43)
    at /home/clicker/node_modules/protractor/built/runner.js:255:30
    at _fulfilled (/home/clicker/node_modules/protractor/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/home/clicker/node_modules/protractor/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/home/clicker/node_modules/protractor/node_modules/q/q.js:796:13)
    at /home/clicker/node_modules/protractor/node_modules/q/q.js:556:49
[14:22:14] E/launcher - Process exited with error code 1
@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 5, 2016

Owner

There's no need to update the webdriver it's done on install.

If you make that change to package.json it should work fine, as it does
here on the image you supplied.

I can send your image back to you tomorrow if it'll help you figure things
out.

On 6 Jul 2016 00:25, "geoHeil" notifications@github.com wrote:

Wow thanks a lot. But still I do not quite get it working:
after a
./node_modules/protractor/bin/webdriver-manager update because only the
global driver was updated
I get the well known timeout that chrome is unreachable:

Finished 'clean-test' after 13 ms
[14:21:12] Starting 'build-e2e'...
[14:21:14] Finished 'build-e2e' after 1.72 s
[14:21:14] I/direct - Using ChromeDriver directly...
[14:21:14] I/launcher - Running 1 instances of WebDriver

/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:27
super(opt_error);
^
WebDriverError: chrome not reachable
(Driver info: chromedriver=2.21.371461 (633e689b520b25f3e264a2ede6b74ccc23cb636a),platform=Linux 4.4.14-moby x86_64)
at WebDriverError (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:27:10)
at Object.checkLegacyResponse (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:580:13)
at /home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:64:13
at Promise.invokeCallback_ (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:1329:14)
at TaskQueue.execute_ (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2790:14)
at TaskQueue.executeNext_ (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2773:21)
at /home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2652:27
at /home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:639:7
at process._tickCallback (node.js:369:9)
From: Task: WebDriver.createSession()
at acquireSession (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:62:22)
at Function.createSession (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:295:12)
at Driver (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/chrome.js:778:38)
at Direct.getNewDriver (/home/clicker/node_modules/protractor/built/driverProviders/direct.js:65:26)
at Runner.createBrowser (/home/clicker/node_modules/protractor/built/runner.js:182:43)
at /home/clicker/node_modules/protractor/built/runner.js:255:30
at _fulfilled (/home/clicker/node_modules/protractor/node_modules/q/q.js:834:54)
at self.promiseDispatch.done (/home/clicker/node_modules/protractor/node_modules/q/q.js:863:30)
at Promise.promise.promiseDispatch (/home/clicker/node_modules/protractor/node_modules/q/q.js:796:13)
at /home/clicker/node_modules/protractor/node_modules/q/q.js:556:49
[14:22:14] E/launcher - Process exited with error code 1


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#114 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AG5tSMn-WQ3KP-eiB7zgaQtZJ8dnGvBXks5qSmlDgaJpZM4JD3xQ
.

Owner

lathonez commented Jul 5, 2016

There's no need to update the webdriver it's done on install.

If you make that change to package.json it should work fine, as it does
here on the image you supplied.

I can send your image back to you tomorrow if it'll help you figure things
out.

On 6 Jul 2016 00:25, "geoHeil" notifications@github.com wrote:

Wow thanks a lot. But still I do not quite get it working:
after a
./node_modules/protractor/bin/webdriver-manager update because only the
global driver was updated
I get the well known timeout that chrome is unreachable:

Finished 'clean-test' after 13 ms
[14:21:12] Starting 'build-e2e'...
[14:21:14] Finished 'build-e2e' after 1.72 s
[14:21:14] I/direct - Using ChromeDriver directly...
[14:21:14] I/launcher - Running 1 instances of WebDriver

/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:27
super(opt_error);
^
WebDriverError: chrome not reachable
(Driver info: chromedriver=2.21.371461 (633e689b520b25f3e264a2ede6b74ccc23cb636a),platform=Linux 4.4.14-moby x86_64)
at WebDriverError (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:27:10)
at Object.checkLegacyResponse (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/error.js:580:13)
at /home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:64:13
at Promise.invokeCallback_ (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:1329:14)
at TaskQueue.execute_ (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2790:14)
at TaskQueue.executeNext_ (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2773:21)
at /home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2652:27
at /home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:639:7
at process._tickCallback (node.js:369:9)
From: Task: WebDriver.createSession()
at acquireSession (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:62:22)
at Function.createSession (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:295:12)
at Driver (/home/clicker/node_modules/protractor/node_modules/selenium-webdriver/chrome.js:778:38)
at Direct.getNewDriver (/home/clicker/node_modules/protractor/built/driverProviders/direct.js:65:26)
at Runner.createBrowser (/home/clicker/node_modules/protractor/built/runner.js:182:43)
at /home/clicker/node_modules/protractor/built/runner.js:255:30
at _fulfilled (/home/clicker/node_modules/protractor/node_modules/q/q.js:834:54)
at self.promiseDispatch.done (/home/clicker/node_modules/protractor/node_modules/q/q.js:863:30)
at Promise.promise.promiseDispatch (/home/clicker/node_modules/protractor/node_modules/q/q.js:796:13)
at /home/clicker/node_modules/protractor/node_modules/q/q.js:556:49
[14:22:14] E/launcher - Process exited with error code 1


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#114 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AG5tSMn-WQ3KP-eiB7zgaQtZJ8dnGvBXks5qSmlDgaJpZM4JD3xQ
.

@geoHeil

This comment has been minimized.

Show comment
Hide comment
@geoHeil

geoHeil Jul 5, 2016

Thanks a lot finally I got it working - well sort of:
1__docker

geoHeil commented Jul 5, 2016

Thanks a lot finally I got it working - well sort of:
1__docker

@lathonez

This comment has been minimized.

Show comment
Hide comment
@lathonez

lathonez Jul 6, 2016

Owner

I've added a little info and a reference to this issue on the e2e blog.

lathonez/lathonez.github.io@2275acf

Owner

lathonez commented Jul 6, 2016

I've added a little info and a reference to this issue on the e2e blog.

lathonez/lathonez.github.io@2275acf

@lathonez lathonez closed this Jul 6, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment