New issue
Advanced search Search tips

Issue 853815 link

Starred by 2 users
Status: Assigned
Owner:
robertma@chromium.org
Cc:
foolip@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Explore setting up a "staging" WPT directory outside external/wpt

Project Member Reported by robertma@chromium.org, Jun 18 2018 
We've received a few requests from Blink engineers to set up a "staging" WPT directory in LayoutTests but outside of external/wpt to have WPT features enabled (especially wptserve) for:

* tests that are being worked on and not ready to be upstreamed (yet)
* tests that use or test Chrome internals which are not suitable for upstreaming but can benefit from wptserve features

It was actually a P3 KR a while ago, also related to issue 347864 (dropping Apache altogether and switching to wptserve), but we haven't got around to work on it. Filing an issue so that we don't forget.

Comment 1 by robertma@chromium.org, Jun 18 2018 

This will be a smaller project and a more conservative approach than issue 347864. Due to the sheer number of existing PHP tests, migrating all of them to wptserve is too much work and doesn't bring much benefit, whereas creating a staging WPT directory and encouraging people to use wptserve instead of PHP for new tests would be more practical.

There are some difficulties in supporting the manifest behaviour. We could generate a separate WPT manifest for this staging directory, but that'd involve some non-trivial amount of wiring & fiddling. An easier solution is to drop manifest support in the staging directory, which means no support for things like ".any.js" or "?variants".

Comment 2 by robertma@chromium.org, Dec 12

Labels: -Pri-3 Pri-2
Owner: robertma@chromium.org
Status: Assigned (was: Available)
More feedback increased the priority of this task. I'll work on this in Q1.
►

Sign in to add a comment