Should we *not* close the tree on forced compile? I guess so. M-A On Fri, Oct 2, 2009 at 7:15 PM, <[email protected]> wrote:
> http://build.chromium.org/buildbot/waterfall/ > > Automatically closing tree for "compile" on "Chromium Builder (dbg)" > > > http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/11423 > > Revision: > Blame list: > > Chromium Builder (dbg) > Build > 11423<http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/11423> > The web-page 'force build' button (clobbered) was pressed by : svnkill > stdio<http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/11423/steps/shell/logs/stdio> > update > scripts > stdio<http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/11423/steps/shell_2/logs/stdio> > taskkill > stdio<http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/11423/steps/shell_3/logs/stdio> > update > stdio<http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/11423/steps/gclient/logs/stdio> > compile > failed > stdio<http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/11423/steps/compile/logs/stdio> > interrupt<http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/11423/steps/compile/logs/interrupt> > warnings<http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/11423/steps/compile/logs/warnings> > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
