summaryrefslogtreecommitdiffstats
path: root/chrome/browser/autocomplete
diff options
context:
space:
mode:
authorphajdan.jr@chromium.org <phajdan.jr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-03-16 13:43:10 +0000
committerphajdan.jr@chromium.org <phajdan.jr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-03-16 13:43:10 +0000
commit9abfae34812add5e6bac420fcd4cc915686afe22 (patch)
tree76b0c26bc62255ccc15600803b7280dc7dc4de7e /chrome/browser/autocomplete
parent40ecc904994be903e4a24d26650739275e5f0f4b (diff)
downloadchromium_src-9abfae34812add5e6bac420fcd4cc915686afe22.zip
chromium_src-9abfae34812add5e6bac420fcd4cc915686afe22.tar.gz
chromium_src-9abfae34812add5e6bac420fcd4cc915686afe22.tar.bz2
This should make ProcessUtilTest.KillSlowChild not-flaky.
There is no need to check process count (which tends to induce flakiness). In fact, we are already checking all important facts: - after checking that process handle is a not-null handle we know that the process started successfully - after WaitForSingleProcess returns true we know that the process finished successfully BUG=8811 Review URL: http://codereview.chromium.org/42224 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11728 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/autocomplete')
0 files changed, 0 insertions, 0 deletions