(3) forks run_webkit_tests.py upstream. (4) Make it possible to run the tests with TestShell while run_webkit_tests.py is upstream. (5) Change the chromium bots to use the upstream run_webkit_tests.py
That all seems fine. But then we have to leave the forked copy in there until the last step (13) is done of making the other tools use the upstream copy. We should minimize as much as possible, the amount of time that we have these scripts forked. Can we move (13) to be (6)? Then we can delete the downstream run_webkit_tests.py. On Tue, Dec 15, 2009 at 5:18 PM, Dirk Pranke <dpra...@chromium.org> wrote: > Hi all, > > A number of us have drawn up a plan for getting the rest of our layout > tests infrastructure upstreamed to webkit.org. You can read about it > here: > > http://www.chromium.org/developers/design-documents/upstreaminglayouttests > > In addition to making us resemble other webkit ports by doing this > (and definitely easing both webkit gardening and our ability to keep > our webkit port from breaking), we also hope to bring added features > to the webkit community. > > We're tentatively hoping to get this all done by the end of Q1 2010. > > Comments to me, Eric Seidel, Dimitry Glazkov, or the list :) > > -- Dirk > > -- > Chromium Developers mailing list: chromium-dev@googlegroups.com > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-dev > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
