falken@ can you me a little background here. What is --enable-wptserver suppose to do? I seem to be able to get the tests pass on my Linux when I run run-webkit-tests script with --enable-wptserver without timeout. Is that any other way to run this option or something else?
The flag is --enable-wptserve (not server). See issue 618366 for more info. This runs the WPT HTTP server rather than Blink's Apache server. The goal is eventually make --enable-wptserve the default flag.
Of course, this is just an FYI bot for now though.
falken@
We did some script injection in testharnessreport.js with some absolute paths. How should we change that to fix serving those with wptserve option? Note that the path to the automation scripts is also out of wpt folder.
Here is the CL that added it:
https://codereview.chromium.org/1994683004/
nzolghadr@: I'm afraid I don't know (I'm not a wptserve expert, but am interested in keeping the bot green because service worker tests will run on this FYI bot).
I think with wptserve a test URL is something like "https?://hostname/pointerevents/...". We need two different handling for "file:///..../imported/wpt/pointerevents/..." and "https?://hostname/pointerevents/...".
I did some investigation.
If a test is served via http://, we can't use file:/// for wpt_automation scripts. This restriction is implemented in both of Blink and Chromium. So bypassing the restriction isn't easy.
We need to serve wpt_automation scripts via http. "serve" command of WPTServe doesn't have a flag / configuration to add URL:directory mapping for now.
A) Call RoutesBuilder.add_mount_point() in serve.py somehow.
B) Run another http server for wpt_automation
Comment 1 by falken@chromium.org
, Jul 11 2016