problem testing e2e in docker image

[geoHeil]

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]

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]

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

[lathonez]

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]

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]

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]

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

[geoHeil]

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]

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]

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]

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

[lathonez]

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]

@geoHeil how can I get root in this image?

EDIT: rebuilding minus the last line as suggested.

[geoHeil]

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]

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]

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.