Re: Switching to new-run-webkit-tests
Adam Barth <abarth <at> webkit.org>
2011-07-01 07:49:54 GMT
Sorry, no switch over tonight. The WebKit2 build is too destroyed to
have any confidence that we're doing things correctly and the Snow
Leopard buildbot appears to have an errant HTTP server bound to port
On Thu, Jun 30, 2011 at 11:47 AM, Adam Barth <abarth <at> webkit.org> wrote:
> According to https://bugs.webkit.org/show_bug.cgi?id=34984, there are
> only two remaining blocking issues:
> 1) Teaching new-run-webkit-tests to understand the difference between
> WebProcess crashes and other sorts of crashes in WebKit2.
> 2) Fixing some issues with the Apple Windows port.
> Once we get (1) fixed (hopefully today), we're going to start moving
> (non-Windows) ports over to new-run-webkit-tests (hopefully tonight).
> I suspect more issues will crop up once we actually flip the switch.
> Please do not hesitate to contact Eric or myself (either via #webkit
> or via bugs.webkit.org). We'll try to respond to any issues that
> arise as quickly as possible.
> Thanks for your patience.
> On Mon, Jun 27, 2011 at 4:26 PM, Xan Lopez <xan <at> gnome.org> wrote:
>> On Tue, Jun 28, 2011 at 1:17 AM, Eric Seidel <eric <at> webkit.org> wrote:
>>> There appear to be 6 remaining blocking issues:
>>> We would like to hear from others who have tried new-run-webkit-tests,
>>> if they have issues which they believe should block migrating to NRWT.
>>> (If so, please file and block the master bug!)
>> I can see the GTK+ port thing with Xvfb is there already, so not a lot
>> to add. NWRT is more sensitive to slow tests than the old
>> infrastructure, so we had to add a bunch of them to the expectations
>> file; I don't think this is particularly bad. In any case with the
>> Xvfb patch and my local expectations file things run beautifully and
>> way faster than before, so looking great from our side!
>>> webkit-dev mailing list
>>> webkit-dev <at> lists.webkit.org
>> webkit-dev mailing list
>> webkit-dev <at> lists.webkit.org