Before you commit it: Would it make sense to stuff this data somewhere outside of the main checkout, like we do in Chrome with the deps/ dir? I know that's a departure from how the WebKit test results currently work, but I also expect people are not going to be too happy about XXXmb of not-useful-to-them data showing up in their checkouts. (I guess a step two of this proposal would be to move the other test results alongside this new location.)
Technical details of this proposal are vague, but I wanted to get it out there before you hit the commit button. :) On Fri, Mar 19, 2010 at 10:13 AM, Dimitri Glazkov <[email protected]> wrote: > WebKit folks, > > We're finally ready to land our port's expected results in the WebKit > tree. It's been a long journey, but we are now to the point where it > no longer makes sense to keep Chromium expectations separate from the > rest of the WebKit. > > It's a pretty large chunk of files, so please bear with us -- you may > experience longer-than-expected checkout time for this commit. > > We are also actively working on porting test_shell (Chromium's test > harness) to DumpRenderTree, to enable running the tests on WebKit > waterfall. > > Until then, you can see test run results on WebKit canaries: > http://build.chromium.org/buildbot/waterfall.fyi/waterfall?branch=&builder=Webkit+(webkit.org)&builder=Webkit+Linux+(webkit.org)&builder=Webkit+Mac+(webkit.org). > > :DG< > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
