I have tried after copying missing .ttf files from Ubuntu 14.04 to 16.04. Then script execution proceeded a bit, but with other errors:

[S7M0215418001177] checking kochi-mincho.ttf[0909/112344:ERROR:md5sum.cc(28)] Could not open file /usr/share/fonts/truetype/kochi/kochi-mincho.ttf
[S7M0215418001177] checking lohit_hi.ttf[0909/112345:ERROR:md5sum.cc(28)] Could not open file /usr/share/fonts/truetype/ttf-indic-fonts-core/lohit_hi.ttf
[S7M0215418001177] checking lohit_ta.ttf[0909/112345:ERROR:md5sum.cc(28)] Could not open file /usr/share/fonts/truetype/ttf-indic-fonts-core/lohit_ta.ttf
[S7M0215418001177] checking MuktiNarrow.ttf[0909/112345:ERROR:md5sum.cc(28)] Could not open file /usr/share/fonts/truetype/ttf-indic-fonts-core/MuktiNarrow.ttf
[S7M0215418001177] checking lohit_pa.ttf[0909/112345:ERROR:md5sum.cc(28)] Could not open file /usr/share/fonts/truetype/ttf-punjabi-fonts/lohit_pa.ttf
[S7M0215418001177] checking resources   

[S7M0215418001177] checking content     
[S7M0215418001177] device prepared   

Starting HTTP server ...apache2: Syntax error on line 30 of /chrome_upstream/src/third_party/WebKit/LayoutTests/http/conf/debian-httpd-2.4.conf: Cannot load modules/libphp5.so into server: /usr/lib/apache2/modules/libphp5.so: cannot open shared object file: No such file or directory

logging httpd errors, if any
httpd returncode None
httpd no stderr handle
httpd no error log

ServerError raised: Failed to start httpd: no pid file found
Traceback (most recent call last):
  File "/chrome_upstream/src/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/run_webkit_tests.py", line 69, in main
    return run(port, options, args, stderr, stdout).exit_code
  File "/chrome_upstream/src/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/run_webkit_tests.py", line 554, in run
    run_details = _run_tests(port, options, args, printer)
  File "/chrome_upstream/src/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/run_webkit_tests.py", line 545, in _run_tests
    return manager.run(args)
  File "/chrome_upstream/src/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/controllers/manager.py", line 130, in run
    self._start_servers(tests_to_run)
  File "/chrome_upstream/src/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/controllers/manager.py", line 380, in _start_servers
    self._port.start_http_server(additional_dirs={}, number_of_drivers=self._options.max_locked_shards)
  File "/chrome_upstream/src/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/android.py", line 625, in start_http_server
    super(AndroidPort, self).start_http_server(additional_dirs, number_of_drivers)
  File "/chrome_upstream/src/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/base.py", line 1162, in start_http_server
    server.start()
  File "/chrome_upstream/src/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/servers/server_base.py", line 104, in start
    self._pid = self._spawn_process()
  File "/chrome_upstream/src/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/servers/apache_http.py", line 147, in _spawn_process
    raise server_base.ServerError('Failed to start %s: no pid file found' % self._name)
ServerError: Failed to start httpd: no pid file found

So, there are two problems:

1. ERROR:md5sum.cc(28)] Could not open file /usr/share/fonts/truetype/...
- Not sure whats causign this.

2. WebKit/LayoutTests/http/conf/debian-httpd-2.4.conf: Cannot load modules/libphp5.so into server

I see, libphp7.0.so in /usr/lib/apache2/modules/ , but not libphp5.so.
By replacing libphp7.0 in WebKit/LayoutTests/http/conf/debian-httpd-2.4.conf, execution proceeded but tests are failed because of renderer crashed.

--------
Starting HTTP server ...                                                                        
Running 1 content_shell.
[0/27] fast/css/variables/accessing-variable-as-named-property.html
[1/27] fast/css/variables/accessing-variable-as-named-property.html failed unexpectedly (renderer crashed)
...
...
---------

This doesn't appear to be a security bug. ccing some random people who might be able to help here.

s.singapati@gmail.com: A fix for this was submitted in November (see  bug 621694 ) - are you still getting this error now?

I think that this is the same as  bug 665515 , and  https://codereview.chromium.org/2740483002/ may fix it; s.singapati@gmail.com can you confirm?