Builds with Chrome are broken on Xenial

[ewallah]

Travis has changed their default OS version from Trusty to Xenial. Running the behat tests with the chrome profile fails:

moodle-plugin-ci behat --profile chrome

Moodle 3.8dev (Build: 20190614), 5dae8c051579b6d79dba4763d45500b049fc0fb5
Php: 7.2.15, pgsql: 9.6.12, OS: Linux 4.15.0-1028-gcp x86_64
Server OS "Linux", Browser: "chrome"
Browser specific fixes have been applied. See http://docs.moodle.org/dev/Acceptance_testing#Browser_specific_fixes
Started at 18-06-2019, 17:49
Selenium server is not running, you need to start it to run tests that involve Javascript. More info in https://docs.moodle.org/dev/Running_acceptance_test

[ewallah]

Chrome is working on Xenial with these additions:

addons:
  chrome: stable
  apt:
    packages:
      - openjdk-8-jre-headless
      - chromium-chromedriver

before_install:
  - ...
  - google-chrome-stable --headless --disable-gpu --remote-debugging-port=9222 http://localhost &

moodle-plugin-ci behat --profile chrome
RUN Behat features for enrol_coursecompleted
Running single behat site:
Moodle 3.8dev (Build: 20190614), 5dae8c051579b6d79dba4763d45500b049fc0fb5
Php: 7.2.15, mysqli: 5.7.25-0ubuntu0.16.04.2, OS: Linux 4.15.0-1028-gcp x86_64
Server OS "Linux", Browser: "chrome"
Browser specific fixes have been applied. See http://docs.moodle.org/dev/Acceptance_testing#Browser_specific_fixes
Started at 18-06-2019, 22:30
...................................................................... 70
...................................................................... 140
...................................................................... 210
...................................................................
6 scenarios (6 passed)
277 steps (277 passed)
5m44.20s (54.19Mb)
The command "moodle-plugin-ci behat --profile chrome" exited with 0.

[ewallah]

Sorry, but the workaround seems to have stopped working with google-chrome-stable (76.0.3809.87-1)

An hour earlier, everything worked fine with google-chrome-stable (75.0.3770.142-1)

[ewallah]

Google-chrome-stable (76.0.3809.100-1) currently works with 127.0.01 instead of localhost

addons:
  chrome: stable
  apt:
    packages:
      - openjdk-8-jre-headless
      - chromium-chromedriver

before_install:
  - ...
  - google-chrome-stable --headless --disable-gpu --remote-debugging-port=9222 http://127.0.0.1 &

[polothy]

Trying to figure out why we need to start Chrome in headless mode now whereas before we didn't. Hard to make sure the changes make sense if that isn't answered.

[kabalin]

See PR #107 and issue #110 for workaround.

[bozoh]

well i just use docker, and works fine, just run

docker run --rm --net=host -d -p4444:4444 selenium/standalone-chrome:lastest