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

Issue 695609 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

system_health.memory_desktop.reference failing on Win Zenbook Perf

Project Member Reported by pras...@chromium.org, Feb 23 2017

Issue description

https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%20Zenbook%20Perf/builds/332/steps/system_health.memory_desktop.reference%20on%20Intel%20GPU%20on%20Windows%20on%20Windows-10-10240
raceback (most recent call last):
  File "c:\b\s\w\irhi1njx\third_party\catapult\telemetry\telemetry\internal\story_runner.py", line 88, in _RunStoryAndProcessErrorIfNeeded
    state.RunStory(results)
  File "c:\b\s\w\irhi1njx\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "c:\b\s\w\irhi1njx\third_party\catapult\telemetry\telemetry\page\shared_page_state.py", line 299, in RunStory
    self._current_page.Run(self)
  File "c:\b\s\w\irhi1njx\third_party\catapult\telemetry\telemetry\page\__init__.py", line 112, in Run
    self.RunPageInteractions(action_runner)
  File "c:\b\s\w\irhi1njx\tools\perf\page_sets\system_health\system_health_story.py", line 122, in RunPageInteractions
    self._Measure(action_runner)
  File "c:\b\s\w\irhi1njx\tools\perf\page_sets\system_health\system_health_story.py", line 105, in _Measure
    action_runner.MeasureMemory(deterministic_mode=True)
  File "c:\b\s\w\irhi1njx\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "c:\b\s\w\irhi1njx\third_party\catapult\telemetry\telemetry\internal\actions\action_runner.py", line 160, in MeasureMemory
    raise exceptions.Error('Unable to obtain memory dump')
Error: Unable to obtain memory dump

c:\b\s\w\irhi1njx\third_party\catapult\telemetry\telemetry\internal\image_processing\_bitmap.py:152: UserWarning: Using pure python png decoder, which could be very slow. To speed up, consider installing numpy & cv2 (OpenCV).
  'Using pure python png decoder, which could be very slow. To speed up, '
INFO:root:Chrome version: 2924
ERROR:root:Error when deleting c:\b\s\w\it7pta90\tmplg3yze, will try again at exit.
Traceback (most recent call last):
  File "c:\b\s\w\irhi1njx\third_party\catapult\telemetry\telemetry\internal\platform\tracing_controller_backend.py", line 285, in CollectAgentTraceData
    os.remove(self._trace_log)
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\b\\s\\w\\it7pta90\\tmplg3yze'
INFO:root:Successfully shut down browser cooperatively
[  FAILED  ] blank:about:blank (11167 ms)

 
Cc: nednguyen@chromium.org
Owner: charliea@chromium.org
Probably related to the recent re-enabling of reference benchmarks?
perezju@, is there any reason why we shouldn't be able to collect a memory dump on the ref build? It was just updated in December.
Cc: primiano@chromium.org
Not that I know of, adding Primiano just in case he remembers something.

If the failures are consistent, could we just disable ref on windows for a while more?
is this a recent regression? on what version it happeened?
If it is very fresh it is possible that this is due to https://codereview.chromium.org/2694083005/ who touched the dump queueing logic.
Sorry, I should have added more context. This is not a regression.

- Memory benchmarks had been disabled for some time since they didn't work on older versions of Chrome.

- The reference version was updated in December.

- Reference benchmarks were enabled again recently, they seem to be working mostly fine on other platforms, but they fail consistently on this Win Zenbook Perf bot.

The error is:

  File "c:\b\s\w\irhi1njx\third_party\catapult\telemetry\telemetry\internal\actions\action_runner.py", line 160, in MeasureMemory
    raise exceptions.Error('Unable to obtain memory dump')
Error: Unable to obtain memory dump

Sorry for not jumping in earlier; i think we actually want to wontfix in favor of  bug 680138 ?
Status: WontFix (was: Untriaged)
sgtm

Sign in to add a comment