| commit | 0f870d922ccb49f23930a4fa30e650eeecb0b686 | |
| author | brucedawson <brucedawson@chromium.org> | |
| Fri, 10 Jul 2015 17:48:31 +0000 (10 10:48 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Fri, 10 Jul 2015 17:50:27 +0000 (10 17:50 +0000) | ||
| tree | f4f352009fa7b7c2ab25685ed88d6a3dffdb5e07 | treesnapshot (tar.gz zip) |
| parent | 690bdb5f1dceb393f539bcac1c8c0175a05cd8ab | commitdiff |
Early-out when the PrivateWorkingSetSnapshot is being flaky
The Pdh APIs which PrivateWorkingSetSnapshot depends on are flaky and
sometimes (~5% of the time on many builders) give back a result of
zero. This is handled seamlessly in task manager by falling back to
the old calculations so it is not a critical failure. Checking for
zero case and skipping the test in that case stops flaky-test
failures.
R=grt@chromium.org,thakis@chromium.org
BUG=508531
Review URL: https://codereview.chromium.org/1225103004
Cr-Commit-Position: refs/heads/master@{#338320}
The Pdh APIs which PrivateWorkingSetSnapshot depends on are flaky and
sometimes (~5% of the time on many builders) give back a result of
zero. This is handled seamlessly in task manager by falling back to
the old calculations so it is not a critical failure. Checking for
zero case and skipping the test in that case stops flaky-test
failures.
R=grt@chromium.org,thakis@chromium.org
BUG=508531
Review URL: https://codereview.chromium.org/1225103004
Cr-Commit-Position: refs/heads/master@{#338320}
| chrome/browser/private_working_set_snapshot_win_unittest.cc | diffblobblamehistory |