Mark some disabled tests as flaky to increase test coverage.

Mark some disabled tests as flaky to increase test coverage.

When a test doesn't hang or crash, it can run on the bots
and on developers' machines.

BUG=none
TEST=none

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=29279

[Erik does not do reviews, 2009-10-16 15:01:50]

http://codereview.chromium.org/269104/diff/1/3
File base/timer_unittest.cc (right):

http://codereview.chromium.org/269104/diff/1/3#newcode321
Line 321: // It's flaky on the buildbot. Bug not filed because this
I'm not sure about this one.  If it doesn't have a bug associated with it, and
the comment seems to indicate that it's not worth trying to fix it, why do
anything?  (actually, why not just delete it altogether since this seems pretty
worthless)  I would still argue that this needs a bug in any case.

http://codereview.chromium.org/269104/diff/1/8
File chrome/test/automation/automation_proxy_uitest.cc (right):

http://codereview.chromium.org/269104/diff/1/8#newcode1074
Line 1074: // This test is flaky, see http://crbug.com/5314. Disabled because it
hangs
There should be a bug number for the mac hang since that seems different than
the flaky bug.

http://codereview.chromium.org/269104/diff/1/9
File net/disk_cache/backend_unittest.cc (right):

http://codereview.chromium.org/269104/diff/1/9#newcode1416
Line 1416: // Flaky, http://crbug.com/21110.
Keep the TODO about adding more debugging info.

[Nicolas Sylvain, 2009-10-16 15:04:07]

I agree with erik's comments, lgtm otherwise. thanks