I have a change out that might make this less flaky. Hopefully. http://codereview.chromium.org/427005
On Fri, Nov 20, 2009 at 6:12 PM, Tim Steele <t...@chromium.org> wrote: > This happened several times (at least 6) throughout the day, alternating > with successful passes. > It seems bad (as in an actual error, rather than a FLAKY_ test) if it > actually takes more than 5 seconds for a new tab, warm or otherwise. > > I filed http://crbug.com/28448 as a perf regression -- not exactly sure > what the protocol is as sheriff for this case. > > [ RUN ] NewTabUIStartupTest.PerfWarm > C:\b\slave\chromium-dbg-builder\build\src\chrome\test\startup\feature_startup_test.cc(91): > error: Value of: window->WaitForTabCountToBecome(3, 5000) > Actual: false > Expected: true > [ FAILED ] NewTabUIStartupTest.PerfWarm (28016 ms) > > > > -- > Chromium Developers mailing list: chromium-dev@googlegroups.com > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-dev -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
