[webkit-dev] Handling failing reftests
ojan at chromium.org
Thu Apr 12 13:33:43 PDT 2012
At that point, we should probably just make it a pixel test? At some level
we just don't have enough experience with reftests to understand what the
common problems with them are and make broad policy recommendations.
On Thu, Apr 12, 2012 at 1:30 PM, Jacob Goldstein <jacobg at adobe.com> wrote:
> Isn't the goal of writing a ref test that it is not platform specific?
> From: Ryosuke Niwa <rniwa at webkit.org>
> Date: Thu, 12 Apr 2012 12:29:42 -0700
> To: Ojan Vafai <ojan at chromium.org>
> Cc: Dirk Pranke <dpranke at chromium.org>, WebKit Development <
> webkit-dev at lists.webkit.org>
> Subject: Re: [webkit-dev] Handling failing reftests
> On Thu, Apr 12, 2012 at 11:53 AM, Ojan Vafai <ojan at chromium.org> wrote:
>> I agree that it's hard sometimes to construct reftests that work, but
>> once you've done so, the cost on the project of maintaining the test is
>> usually considerably lower than pixel tests.
> Not so sure. There are cases where we have these platform specific
> failures for ref tests, and they're much harder to fix than rebaselining
> pixel results.
> - Ryosuke
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev