Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(28)

Issue 486037: Add a regression test for http://crbug.com/29473 (Closed)

Created:
11 years ago by Evan Stade
Modified:
9 years, 6 months ago
Reviewers:
tony, jcampan
CC:
chromium-reviews_googlegroups.com, ben+cc_chromium.org, Paweł Hajdan Jr.
Visibility:
Public.

Description

Add a regression test for http://crbug.com/29473 BUG=29473 TEST=it passes Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=34504

Patch Set 1 #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats (+32 lines, -2 lines) Patch
M chrome/browser/browser_focus_uitest.cc View 2 chunks +32 lines, -2 lines 2 comments Download

Messages

Total messages: 7 (0 generated)
Evan Stade
11 years ago (2009-12-11 21:50:55 UTC) #1
tony
LGTM http://codereview.chromium.org/486037/diff/1/2 File chrome/browser/browser_focus_uitest.cc (right): http://codereview.chromium.org/486037/diff/1/2#newcode300 chrome/browser/browser_focus_uitest.cc:300: for (int j = 0; j < 25; ...
11 years ago (2009-12-11 22:00:35 UTC) #2
Evan Stade
http://codereview.chromium.org/486037/diff/1/2 File chrome/browser/browser_focus_uitest.cc (right): http://codereview.chromium.org/486037/diff/1/2#newcode300 chrome/browser/browser_focus_uitest.cc:300: for (int j = 0; j < 25; j++) ...
11 years ago (2009-12-11 22:11:59 UTC) #3
tony
<1s is fast, seems fine to keep it at 25.
11 years ago (2009-12-11 22:15:28 UTC) #4
Evan Stade
(actually, it takes me 3.399s, I can reduce it if you want, but we have ...
11 years ago (2009-12-11 22:26:43 UTC) #5
jcampan
LGTM but I think it'd be better to lower the 25 iterations to a value ...
11 years ago (2009-12-11 22:41:34 UTC) #6
Evan Stade
11 years ago (2009-12-14 22:02:20 UTC) #7
ok, I was more careful with my experiments. Without any changes, this test takes
about 2.5 seconds on my machine. Most of that time is spinning up and shutting
down of the test, not running of the test.  With these changes, it seems to be
sitting at ~5 seconds (I don't know why it changed from 3.5 to 5 over the
weekend, but this is not a controlled environment). Lowering the iterations to
15 gets it to about 4 (1.5 second slowdown). I'll go with that.

Powered by Google App Engine
This is Rietveld 408576698