[prev in list] [next in list] [prev in thread] [next in thread] 

List:       webkit-dev
Subject:    Re: [webkit-dev] Top 100 sites browsing tests proprosal
From:       Ryosuke Niwa <rniwa () webkit ! org>
Date:       2012-04-30 18:19:45
Message-ID: CABNRm63gUDzeY3mg0ztjduZznVY=-Gq+9DA4FT0Byv9mtJ0xXw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Mon, Apr 30, 2012 at 3:29 AM, Sergio Villar Senin <svillar@igalia.com>wrote:

> En 27/04/12 01:19, Ryosuke Niwa escribiu:
> > See my posts about archive.org-based performance tests. We can use the
> > same infrastructure to make sure WebKit doesn't crash :)
>
> Yeah that's great! I just forgot to replay to that thread :)
>
> > In fact... running top 100 websites as performance tests might just do
> > the trick because we'll catch any crashes (can't catch assertion
> > failures though :( ).
>
> Having performance tests will indeed catch the "obvious" crashes, but I
> was not specially concerned about them because our Layout tests would
> likely catch them first. I was mainly interested in assertions. Why not
> just use debug builds with the same cool infrastructure you're
> developing and call it top-100/assertion/whatever tests?
>

Possible but we'll likely need a separate bot for that. If you're
interested in this idea, please file a bug.

- Ryosuke

[Attachment #5 (text/html)]

<div class="gmail_quote">On Mon, Apr 30, 2012 at 3:29 AM, Sergio Villar Senin <span \
dir="ltr">&lt;<a href="mailto:svillar@igalia.com" \
target="_blank">svillar@igalia.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">

En 27/04/12 01:19, Ryosuke Niwa escribiu:<br>
<div class="im">&gt; See my posts about archive.org-based performance tests. We can \
use the<br> &gt; same infrastructure to make sure WebKit doesn&#39;t crash :)<br>
<br>
</div>Yeah that&#39;s great! I just forgot to replay to that thread :)<br>
<div class="im"><br>
&gt; In fact... running top 100 websites as performance tests might just do<br>
&gt; the trick because we&#39;ll catch any crashes (can&#39;t catch assertion<br>
&gt; failures though :( ).<br>
<br>
</div>Having performance tests will indeed catch the &quot;obvious&quot; crashes, but \
I<br> was not specially concerned about them because our Layout tests would<br>
likely catch them first. I was mainly interested in assertions. Why not<br>
just use debug builds with the same cool infrastructure you&#39;re<br>
developing and call it top-100/assertion/whatever \
tests?<br></blockquote><div><br></div><div>Possible but we&#39;ll likely need a \
separate bot for that. If you&#39;re interested in this idea, please file a \
bug.</div><div>

<br></div><div>- Ryosuke</div><div><br></div></div>



_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


[prev in list] [next in list] [prev in thread] [next in thread]