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 <[email protected]> wrote: > Isn't the goal of writing a ref test that it is not platform specific? > > From: Ryosuke Niwa <[email protected]> > Date: Thu, 12 Apr 2012 12:29:42 -0700 > To: Ojan Vafai <[email protected]> > Cc: Dirk Pranke <[email protected]>, WebKit Development < > [email protected]> > Subject: Re: [webkit-dev] Handling failing reftests > > On Thu, Apr 12, 2012 at 11:53 AM, Ojan Vafai <[email protected]> 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 > >
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
