New issue
Advanced search Search tips

Issue 842173 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Jun 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

media.desktop/video.html?src=crowd.ogg&type=audio in media.desktop failing on chromium.perf/Win 10 Perf

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, May 11 2018

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of charliea@chromium.org

media.desktop/video.html?src=crowd.ogg&type=audio in media.desktop failing on chromium.perf/Win 10 Perf

Builders failed on: 
- Win 10 Perf: 
  https://ci.chromium.org/buildbot/chromium.perf/Win%2010%20Perf

It looks like it's been flaky for a while (past ~50 runs) with the following error:

Traceback (most recent call last):
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\story_runner.py", line 123, in _RunStoryAndProcessErrorIfNeeded
    state.RunStory(results)
  File "c:\b\s\w\ir\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\ir\third_party\catapult\telemetry\telemetry\page\shared_page_state.py", line 331, in RunStory
    self._current_page.Run(self)
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\page\__init__.py", line 97, in Run
    self.RunPageInteractions(action_runner)
  File "c:\b\s\w\ir\tools\perf\page_sets\media_cases.py", line 103, in RunPageInteractions
    action_runner.MeasureMemory()
  File "c:\b\s\w\ir\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\ir\third_party\catapult\telemetry\telemetry\internal\actions\action_runner.py", line 162, in MeasureMemory


    raise exceptions.StoryActionError('Unable to obtain memory dump')
StoryActionError: Unable to obtain memory dump

(CCing Juan to see if he has any further info on my it might be failing to collect a memory dump.)

I don't think this flakiness (3 failures in last ~50 runs) meets the threshold for disabling, but warrants an investigation. Benchmark owners, could you try to figure out why this benchmark is failing?
 
Status: Fixed (was: Available)
no longer failing

Sign in to add a comment