Should we be archiving perf tests so we can backtrack these regressions more easily? For instance, Windows archives some tests (e.g. http://build.chromium.org/buildbot/continuous/LATEST/chrome-win32.test/), though startup isn't one of them.
Michael On Thu, Sep 3, 2009 at 9:47 AM, Michael Moss<mm...@chromium.org> wrote: > The bot that builds and runs these tests is a dedicated 32-bit machine. > > On Thu, Sep 3, 2009 at 9:38 AM, Evan Martin<e...@chromium.org> wrote: >> >> On Thu, Sep 3, 2009 at 9:33 AM, Brett Wilson<bre...@chromium.org> wrote: >>> On Thu, Sep 3, 2009 at 9:26 AM, Evan Martin<e...@chromium.org> wrote: >>>> Ok, I'll mark that I own this here and unassign it if I can't figure it >>>> out: >>>> http://code.google.com/p/chromium/issues/detail?id=20991 >>>> >>>> On Thu, Sep 3, 2009 at 2:41 AM, Dean McNamee<de...@chromium.org> wrote: >>>>> Ug, I can't reproduce this on my desktop. If I had to take a guess, I >>>>> would guess Brett's gfx::Font change. >>> >>> It could be my font change. It does measure some extra text on >>> startup. But I would have thought this was nothing compared to the >>> text we already measure. >> >> Random idea: did someone switch our builders to build 64-bit binaries now? >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
