content_shell seems times out for automated wpt inputs |
||||||
Issue descriptionWhen I run ./third_party/WebKit/Tools/Scripts/run-webkit-tests external/wpt/pointerevents/pointerevent_attributes_hoverable_pointers-manual.html the test passes just fine. But when I run ./out/Release/content_shell --run-layout-test external/wpt/pointerevents/pointerevent_attributes_hoverable_pointers-manual.html it is stuck without doing anything. It is almost impossible to debug the page or the automation instructions using the run-webkit-tests.
,
Feb 4 2017
Confirmed. Possible workaround: 1. Run ./third_party/WebKit/Tools/Scripts/run-blink-wptserve 2. Open http://localhost:8081/pointerevents/pointerevent_attributes_hoverable_pointers-manual.html (Does that work OK for now for debugging this test?
,
Feb 7 2017
The suggested way doesn't load the automation scripts I believe. I mean it just loads the test similar to ./serve command under web-platform-tests repo. At least that is what happened to me.
,
Mar 23 2017
Any update on this?
,
Mar 28 2017
I suspect that it's the loadAutomationScript() in testharnessreport.js that's going wrong, the paths may end up looking differently. For it to work over HTTP, the hostname has to be web-platform.test, so try if http://web-platform.test:8081/pointerevents/pointerevent_attributes_hoverable_pointers-manual.html works.
,
Jan 9 2018
nzolghadr@, have you kept having trouble with this? Downgrading to a P3 since it seems like it'd be OK to keep not fixing it for a while, and likely that the whole wpt_automation mechanism might go away first, in favor of testdriver.js upstream.
,
Jan 9 2018
That's alright. Sounds good.
,
Jan 10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 16
nzolghadr@ lanwei@ will this be fixed by the ongoing work on the actions API? |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by nzolghadr@chromium.org
, Feb 3 2017