| commit | 49e41a17f19b767a23da94ffdc9ca5b15d9c0d5f | [log] [tgz] |
|---|---|---|
| author | skyostil@chromium.org <skyostil@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | Wed Aug 06 16:23:25 2014 |
| committer | skyostil@chromium.org <skyostil@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | Wed Aug 06 16:23:25 2014 |
| tree | a680dc71d5087c1013e33a0c48ac84b17d669d28 | |
| parent | 98dd29fe9a7564ce1e5104df87d769fe2a740a83 [diff] |
[telemetry] Disable IPPET power monitor Disable IPPET power monitor added in https://codereview.chromium.org/394923003/. The win8 perf bot (http://build.chromium.org/p/chromium.perf/builders/Win%208%20Perf%20%281%29) became pretty flaky right after this power monitoring patch landed. Some of the failures are clearly IPPET-related, but others are silent timeouts which also appeared around the same time. Sample failures: - AssertionError: Called StartMonitoringPower() twice. http://build.chromium.org/p/chromium.perf/builders/Win%208%20Perf%20%281%29/builds/2561/steps/page_cycler.dhtml/logs/stdio - IppetError: Timed out waiting for IPPET to close. http://build.chromium.org/p/chromium.perf/builders/Win%208%20Perf%20%281%29/builds/2540/steps/page_cycler.dhtml/logs/stdio - TimeoutException: Timed out while waiting 5s for IppetServerIsUp. http://build.chromium.org/p/chromium.perf/builders/Win%208%20Perf%20%281%29/builds/2551/steps/page_cycler.dhtml/logs/stdio - Generic timeout http://build.chromium.org/p/chromium.perf/builders/Win%208%20Perf%20%281%29/builds/2558/steps/page_cycler.intl_ar_fa_he/logs/stdio Original issue's description: > [telemetry] Add IPPET power monitor. > > This power monitor lets our automated testers track power usage on Windows on Intel Sandy Bridge or later. > > > BUG=336558, 153139 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=286541 R=rmcilroy@chromium.org, tonyg@chromium.org Review URL: https://codereview.chromium.org/443973002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@287779 0039d316-1c4b-4281-b951-d872f2087c98