Fix CI

[Can Kattwinkel]

Running with gitlab-runner 11.5.0 (3afdaba6)
on docker-auto-scale 72989761
Using Docker executor with image weboaks/node-karma-protractor-chrome ...
Pulling docker image weboaks/node-karma-protractor-chrome ...
Using docker image sha256:5bc06b25a1cddcbbcfa37b307de185eded21b4230703b2e456e386e79f8c360b for weboaks/node-karma-protractor-chrome ...
Running on runner-72989761-project-7686814-concurrent-0 via runner-72989761-srm-1546682107-eb850e3b...
Cloning repository...
Cloning into '/builds/w11k-es/angular-sticky-things'...
Checking out 82e3ac1 as master...
Skipping Git submodules setup
Downloading artifacts for build-lib (140215144)...
Downloading artifacts from coordinator... ok id=140215144 responseStatus=200 OK token=xDyKmt2P
$ npm install -g npm@latest
/usr/bin/npm -> /usr/lib/node_modules/npm/bin/npm-cli.js
/usr/bin/npx -> /usr/lib/node_modules/npm/bin/npx-cli.js

• npm@6.5.0
  added 2 packages from 1 contributor and updated 14 packages in 26.733s
  $ npm ci

fsevents@1.2.4 install /builds/w11k-es/angular-sticky-things/node_modules/fsevents
node install

node-sass@4.9.3 install /builds/w11k-es/angular-sticky-things/node_modules/node-sass
node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.9.3/linux-x64-64_binding.node
Download complete
Binary saved to /builds/w11k-es/angular-sticky-things/node_modules/node-sass/vendor/linux-x64-64/binding.node
Caching binary to /root/.npm/node-sass/4.9.3/linux-x64-64_binding.node

node-sass@4.9.3 postinstall /builds/w11k-es/angular-sticky-things/node_modules/node-sass
node scripts/build.js

Binary found at /builds/w11k-es/angular-sticky-things/node_modules/node-sass/vendor/linux-x64-64/binding.node
Testing binary
Binary is fine
added 1368 packages in 22.589s
$ npm run e2e

angular-sticky-things-demo@1.1.0 e2e /builds/w11k-es/angular-sticky-things
ng e2e

** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **

Date: 2019-01-05T09:58:02.163Z
Hash: 503158fe4ea9da355176
Time: 14222ms
chunk {main} main.js, main.js.map (main) 54.2 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 227 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 5.22 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 184 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 3.53 MB [initial] [rendered]
[09:58:02] I/file_manager - creating folder /builds/w11k-es/angular-sticky-things/node_modules/protractor/node_modules/webdriver-manager/selenium
[09:58:02] I/config_source - curl -o/builds/w11k-es/angular-sticky-things/node_modules/protractor/node_modules/webdriver-manager/selenium/chrome-response.xml https://chromedriver.storage.googleapis.com/
ℹ ｢wdm｣: Compiled successfully.
[09:58:02] I/downloader - curl -o/builds/w11k-es/angular-sticky-things/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.45.zip https://chromedriver.storage.googleapis.com/2.45/chromedriver_linux64.zip
[09:58:02] I/update - chromedriver: unzipping chromedriver_2.45.zip
[09:58:03] I/update - chromedriver: setting permissions to 0755 for /builds/w11k-es/angular-sticky-things/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.45
(node:109) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
[09:58:03] I/launcher - Running 1 instances of WebDriver
[09:58:03] I/direct - Using ChromeDriver directly...
[09:58:07] E/launcher - session not created: Chrome version must be between 70 and 73
(Driver info: chromedriver=2.45.615279 (12b89733300bd268cff3b78fc76cb8f3a7cc44e5),platform=Linux 4.14.48-coreos-r2 x86_64)
[09:58:07] E/launcher - SessionNotCreatedError: session not created: Chrome version must be between 70 and 73
(Driver info: chromedriver=2.45.615279 (12b89733300bd268cff3b78fc76cb8f3a7cc44e5),platform=Linux 4.14.48-coreos-r2 x86_64)
at Object.checkLegacyResponse (/builds/w11k-es/angular-sticky-things/node_modules/selenium-webdriver/lib/error.js:546:15)
at parseHttpResponse (/builds/w11k-es/angular-sticky-things/node_modules/selenium-webdriver/lib/http.js:509:13)
at doSend.then.response (/builds/w11k-es/angular-sticky-things/node_modules/selenium-webdriver/lib/http.js:441:30)
at process._tickCallback (internal/process/next_tick.js:68:7)
From: Task: WebDriver.createSession()
at Function.createSession (/builds/w11k-es/angular-sticky-things/node_modules/selenium-webdriver/lib/webdriver.js:769:24)
at Function.createSession (/builds/w11k-es/angular-sticky-things/node_modules/selenium-webdriver/chrome.js:761:15)
at Direct.getNewDriver (/builds/w11k-es/angular-sticky-things/node_modules/protractor/built/driverProviders/direct.js:77:33)
at Runner.createBrowser (/builds/w11k-es/angular-sticky-things/node_modules/protractor/built/runner.js:195:43)
at q.then.then (/builds/w11k-es/angular-sticky-things/node_modules/protractor/built/runner.js:339:29)
at _fulfilled (/builds/w11k-es/angular-sticky-things/node_modules/q/q.js:834:54)
at /builds/w11k-es/angular-sticky-things/node_modules/q/q.js:863:30
at Promise.promise.promiseDispatch (/builds/w11k-es/angular-sticky-things/node_modules/q/q.js:796:13)
at /builds/w11k-es/angular-sticky-things/node_modules/q/q.js:556:49
at runSingle (/builds/w11k-es/angular-sticky-things/node_modules/q/q.js:137:13)
[09:58:07] E/launcher - Process exited with error code 199
An unexpected error occurred: undefined
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! angular-sticky-things-demo@1.1.0 e2e: ng e2e
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the angular-sticky-things-demo@1.1.0 e2e script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-01-05T09_58_07_170Z-debug.log
(EE)
Fatal server error:
(EE) Server is already active for display 99
If this server is no longer running, remove /tmp/.X99-lock
and start again.
(EE)
ERROR: Job failed: exit code 1