[webkit-dev] Chromium layout test expectations coming today
ojan at chromium.org
Fri Mar 19 17:30:20 PDT 2010
Currently we do BUG12345 for Chromium bugs. There are no WebKit bugs listed.
How about we instead use CR12345 for Chromium bugs and WK12345 for WebKit
On Sat, Mar 20, 2010 at 12:09 AM, Darin Fisher <darin at chromium.org> wrote:
> platform/chromium/test_expectations.txt contains bug references to
> crbug.com. I presume that newly filed bugs will be in bugs.webkit.orginstead. Unfortunately, it is going to be a bit hard to tell the difference
> given only the bug number. Is there a system we should use to annotate the
> (congrats guys for getting this done!)
> On Fri, Mar 19, 2010 at 4:38 PM, Dimitri Glazkov <dglazkov at chromium.org>wrote:
>> The expectations are in as of r56278. Huge thanks to Dirk Pranke for
>> battling svn all day!
>> On Fri, Mar 19, 2010 at 10:13 AM, Dimitri Glazkov <dglazkov at chromium.org>
>> > 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:
>> > :DG<
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev