New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 596067 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression

Blocked on:
issue 595744



Sign in to add a comment

page_cycler.basic_oopif flaky on Win Zenbook Perf (4)

Project Member Reported by petrcermak@chromium.org, Mar 18 2016

Issue description

Revision range first seen: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%20Zenbook%20Perf%20%284%29/builds/1123
Link to failing step log: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%20Zenbook%20Perf%20%284%29/builds/1123/steps/page_cycler.basic_oopif/logs/stdio

In all cases, the test failed on http://www.nationalgeographic.com/:


[ RUN      ] http://www.nationalgeographic.com/
(INFO) 2016-03-17 11:16:42,055 power._StopInternal:48  Attempting to stop non-running monitor
(INFO) 2016-03-17 11:16:42,954 power.Start:93  Start: PowerMetric running
(INFO) 2016-03-17 11:16:47,877 power._StopInternal:51  StopInternal: PowerMetric running
Traceback (most recent call last):
  File "C:\b\build\slave\Win_Zenbook_Perf__4_\build\src\third_party\catapult\telemetry\telemetry\internal\story_runner.py", line 84, in _RunStoryAndProcessErrorIfNeeded
    state.RunStory(results)
  File "C:\b\build\slave\Win_Zenbook_Perf__4_\build\src\third_party\catapult\telemetry\telemetry\page\shared_page_state.py", line 331, in RunStory
    self._current_page, self._current_tab, results)
  File "C:\b\build\slave\Win_Zenbook_Perf__4_\build\src\tools\perf\measurements\page_cycler.py", line 125, in ValidateAndMeasurePage
    self._power_metric.Stop(page, tab)
  File "C:\b\build\slave\Win_Zenbook_Perf__4_\build\src\tools\perf\metrics\power.py", line 100, in Stop
    self._StopInternal()
  File "C:\b\build\slave\Win_Zenbook_Perf__4_\build\src\tools\perf\metrics\power.py", line 52, in _StopInternal
    self._results = self._platform.StopMonitoringPower()
  File "C:\b\build\slave\Win_Zenbook_Perf__4_\build\src\third_party\catapult\telemetry\telemetry\core\platform.py", line 292, in StopMonitoringPower
    ret_val = self._platform_backend.StopMonitoringPower()
  File "C:\b\build\slave\Win_Zenbook_Perf__4_\build\src\third_party\catapult\telemetry\telemetry\internal\platform\win_platform_backend.py", line 342, in StopMonitoringPower
    return self._power_monitor.StopMonitoringPower()
  File "C:\b\build\slave\Win_Zenbook_Perf__4_\build\src\third_party\catapult\telemetry\telemetry\internal\platform\power_monitor\msr_power_monitor.py", line 141, in StopMonitoringPower
    power_statistics = super(MsrPowerMonitorWin, self).StopMonitoringPower()
  File "C:\b\build\slave\Win_Zenbook_Perf__4_\build\src\third_party\catapult\telemetry\telemetry\internal\platform\power_monitor\msr_power_monitor.py", line 51, in StopMonitoringPower
    energy_consumption_j = self._PackageEnergyJoules() - self._start_energy_j
  File "C:\b\build\slave\Win_Zenbook_Perf__4_\build\src\third_party\catapult\telemetry\telemetry\internal\platform\power_monitor\msr_power_monitor.py", line 73, in _PackageEnergyJoules
    return (self._backend.ReadMsr(MSR_PKG_ENERGY_STATUS, 0, 32) *
  File "C:\b\build\slave\Win_Zenbook_Perf__4_\build\src\third_party\catapult\telemetry\telemetry\internal\platform\win_platform_backend.py", line 382, in ReadMsr
    response = sock.recv(8)
timeout: timed out

(INFO) 2016-03-17 11:16:59,664 power.Close:104  Closing power monitors
(INFO) 2016-03-17 11:16:59,665 platform.IsMonitoringPower:299  IsMonitoringPower: True
(INFO) 2016-03-17 11:16:59,665 exception_formatter.PrintFormattedException:20  Try printing formatted exception: None None None

Exception raised when cleaning story run: 

Traceback (most recent call last):
  _RunStoryAndProcessErrorIfNeeded at third_party\catapult\telemetry\telemetry\internal\story_runner.py:110
    test.DidRunPage(state.platform)
  DidRunPage at tools\perf\measurements\page_cycler.py:156
    self._power_metric.Close()
  Close at tools\perf\metrics\power.py:106
    self._platform.StopMonitoringPower()
  StopMonitoringPower at third_party\catapult\telemetry\telemetry\core\platform.py:292
    ret_val = self._platform_backend.StopMonitoringPower()
  StopMonitoringPower at third_party\catapult\telemetry\telemetry\internal\platform\win_platform_backend.py:342
    return self._power_monitor.StopMonitoringPower()
  StopMonitoringPower at third_party\catapult\telemetry\telemetry\internal\platform\power_monitor\msr_power_monitor.py:141
    power_statistics = super(MsrPowerMonitorWin, self).StopMonitoringPower()
  StopMonitoringPower at third_party\catapult\telemetry\telemetry\internal\platform\power_monitor\msr_power_monitor.py:50
    self._CheckStop()
  _CheckStop at third_party\catapult\telemetry\telemetry\internal\platform\power_monitor\__init__.py:35
    assert self._monitoring, "Not monitoring power."
AssertionError: Not monitoring power.

Locals:
  No locals!

[  FAILED  ] http://www.nationalgeographic.com/ (18437 ms)


Despite failing more than once in five runs in the past 10 runs (https://chromium.googlesource.com/chromium/src/+/master/tools/perf/docs/perf_bot_sheriffing.md#testfailures), I'm not going to disable the test at this point because it would have to be disabled on all Windows perf bots ( Issue 595744 ). Instead, I'm assigning it to the test owner for further investigation. Please disable the test if it starts failing more often (or on more bots). If the test is disabled, please downgrade to Pri-2.

 
Project Member

Comment 1 by bugdroid1@chromium.org, Mar 18 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/15047b716f232fc75525e4afdd81eb892da75640

commit 15047b716f232fc75525e4afdd81eb892da75640
Author: nednguyen <nednguyen@google.com>
Date: Fri Mar 18 20:19:19 2016

Disable page_cycler.basic_oopif on zenbook bot

BUG= 596067 ,  595744 

Review URL: https://codereview.chromium.org/1815243002

Cr-Commit-Position: refs/heads/master@{#382065}

[modify] https://crrev.com/15047b716f232fc75525e4afdd81eb892da75640/tools/perf/benchmarks/page_cycler.py

Cc: dtu@chromium.org nasko@chromium.org
Owner: nedngu...@google.com
I probably will just increase the timeout amount here.
Project Member

Comment 3 by bugdroid1@chromium.org, Mar 20 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/88167f9e85f7b897deab1ce4b4ff93146f03d32b

commit 88167f9e85f7b897deab1ce4b4ff93146f03d32b
Author: nednguyen <nednguyen@google.com>
Date: Sun Mar 20 20:24:57 2016

Revert of Disable page_cycler.basic_oopif on zenbook bot (patchset #3 id:40001 of https://codereview.chromium.org/1815243002/ )

Reason for revert:
Did not disable the benchmark:
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%20Zenbook%20Perf%20%284%29/builds/1150

Original issue's description:
> Disable page_cycler.basic_oopif on zenbook bot
>
> BUG= 596067 ,  595744 
>
> Committed: https://crrev.com/15047b716f232fc75525e4afdd81eb892da75640
> Cr-Commit-Position: refs/heads/master@{#382065}

TBR=petrcermak@chromium.org,eakuefner@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG= 596067 ,  595744 

Review URL: https://codereview.chromium.org/1819743002

Cr-Commit-Position: refs/heads/master@{#382229}

[modify] https://crrev.com/88167f9e85f7b897deab1ce4b4ff93146f03d32b/tools/perf/benchmarks/page_cycler.py

Status: Fixed (was: Assigned)
Should be fixed with https://codereview.chromium.org/1816873002/

Sign in to add a comment