On Jul 7, 2011, at 2:55 AM, Eric Seidel wrote:
> One of the Leopard Debug slaves (apple-mac-pro-6) is still wedged
> after the transition:
> http://build.webkit.org/builders/Leopard%20Intel%20Debug%20%28Tests%29/builds/32142/steps/layout-test/logs/stdio
>
> If someone could run killall httpd, or
One of the Leopard Debug slaves (apple-mac-pro-6) is still wedged
after the transition:
http://build.webkit.org/builders/Leopard%20Intel%20Debug%20%28Tests%29/builds/32142/steps/layout-test/logs/stdio
If someone could run killall httpd, or just restart the machine,
that'd be wonderful. :)
In othe
On Wed, Jul 6, 2011 at 9:04 AM, Xan Lopez wrote:
> On Wed, Jul 6, 2011 at 5:58 PM, Adam Roben wrote:
>> On Jul 6, 2011, at 11:53 AM, Adam Roben wrote:
>>
>>> Now that more and more ports are switching to NRWT, it would be great for
>>> someone to explain what the best practices are for dealing w
On Wed, Jul 6, 2011 at 5:58 PM, Adam Roben wrote:
> On Jul 6, 2011, at 11:53 AM, Adam Roben wrote:
>
>> Now that more and more ports are switching to NRWT, it would be great for
>> someone to explain what the best practices are for dealing with failing and
>> flaky tests.
>
> Two specific questi
On Jul 6, 2011, at 11:53 AM, Adam Roben wrote:
> Now that more and more ports are switching to NRWT, it would be great for
> someone to explain what the best practices are for dealing with failing and
> flaky tests.
Two specific questions I have:
1) Are the ports that have switched to NRWT no
Now that more and more ports are switching to NRWT, it would be great for
someone to explain what the best practices are for dealing with failing and
flaky tests.
-Adam
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/ma
Xan and I found the issue regarding the timeouts, and Xan is trying
NRWT again on the machine:
https://bugs.webkit.org/show_bug.cgi?id=63983
On Wed, Jul 6, 2011 at 2:20 AM, Xan wrote:
> On Wed, Jul 6, 2011 at 11:10 AM, Eric Seidel wrote:
>> Update:
>>
>> Leopard Release, Gtk and Qt have been suc
No problem. I leave it in your hands to re-transition, since you're
much more familiar with the platform than I.
It was faling before the move, and failing again after. :) The bots
have simply been red today.
I'm happy to work with you to update the skipped lists.
-eric
On Wed, Jul 6, 2011 at
[Sending with the right address...]
On Wed, Jul 6, 2011 at 11:10 AM, Eric Seidel wrote:
> Update:
>
> Leopard Release, Gtk and Qt have been successfully transitioned.
What do we exactly consider successfully transitioned? The GTK+ bots
were still failing, so I reverted to the old script. At the
Update:
Leopard Release, Gtk and Qt have been successfully transitioned.
The Leopard Debug bot has a stray httpd process (without corresponding
/tmp/WebKit/httpd.pid) and will require manual intervention:
http://build.webkit.org/builders/Leopard%20Intel%20Debug%20%28Tests%29/builds/32086/steps/la
Update:
Snow Leopard - Successful transition.
Leopard - Had to roll-back due to a bug in webkitdirs.pm which errors
in both ORWT and NRWT, but causes NRWT to fail hard.
https://bugs.webkit.org/show_bug.cgi?id=63973
Gtk - Bot seems hard-hung (unclear if NRWT related). Waiting for
assistance from a
We've turned NRWT back on for the WebKit1 Snow Leopard bots. We
believe we've solved the http-lock issue and will be monitoring the
bots.
-eric
On Fri, Jul 1, 2011 at 5:54 PM, Adam Barth wrote:
> Thanks for your patience with the disruptions on the tree today. The
> bots are having some troubl
Thanks for your patience with the disruptions on the tree today. The
bots are having some trouble with the HTTP lock that don't manifest
locally or on our test slave. I've turned NRWT back off while we try
to sort that out.
Thanks,
Adam
On Fri, Jul 1, 2011 at 12:49 AM, Adam Barth wrote:
> Sor
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
8080. :(
Adam
On Thu, Jun 30, 2011 at 11:47 AM, Adam Barth wrote:
> According to https:/
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
On Tue, Jun 28, 2011 at 1:17 AM, Eric Seidel wrote:
> There appear to be 6 remaining blocking issues:
> https://bugs.webkit.org/showdependencytree.cgi?id=34984&hide_resolved=1
>
> We would like to hear from others who have tried new-run-webkit-tests,
> if they have issues which they believe should
Looking at the master bug, it looks like we're close to switching the
project to new-run-webkit-tests:
https://bugs.webkit.org/show_bug.cgi?id=34984
There appear to be 6 remaining blocking issues:
https://bugs.webkit.org/showdependencytree.cgi?id=34984&hide_resolved=1
We would like to hear from o
17 matches
Mail list logo
