Hello,
for us too, as many of you poited out before me, the main issue is not
build breakage while maintaining the QtWebKit buildbot - because these
are most of the time trivial fixes - but tracking down the previously
passing but after-the-night failing tests.
Because of the timezone
Eric and I are working on a bot that might help this situation.
Essentially, the bot will try out patches on Qt and GTK and add a
comment to the bug if the patch regresses the build. Our plan is to
start with compiling, but we'd eventually like to run the tests as
well.
Of course, the bots won't
On Mon, 2009-11-16 at 05:24 -0800, Adam Barth wrote:
Eric and I are working on a bot that might help this situation.
Essentially, the bot will try out patches on Qt and GTK and add a
comment to the bug if the patch regresses the build. Our plan is to
start with compiling, but we'd eventually
On Mon, Nov 16, 2009 at 3:33 PM, Gustavo Noronha Silva g...@gnome.org wrote:
On Mon, 2009-11-16 at 05:24 -0800, Adam Barth wrote:
Eric and I are working on a bot that might help this situation.
Essentially, the bot will try out patches on Qt and GTK and add a
comment to the bug if the patch
On Mon, Nov 16, 2009 at 5:56 AM, Xan Lopez x...@gnome.org wrote:
On Mon, Nov 16, 2009 at 3:33 PM, Gustavo Noronha Silva g...@gnome.org wrote:
On Mon, 2009-11-16 at 05:24 -0800, Adam Barth wrote:
Eric and I are working on a bot that might help this situation.
Essentially, the bot will try out
On Mon, Nov 16, 2009 at 12:47 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
This is a huge issue with the Chromium port as well. We spend quite a
bit of effort tracking down failing tests, only to discover that the
failure is due to one-port baselines or new functionality added to
DRT. I
6 matches
Mail list logo
