Randy, if I'm reading this right, the failing story was re-enabled in https://codereview.chromium.org/2362243002/

Is there any way to disable the test case just for svelte?

Revision range first seen:420645:420688

Link to failing step log:
https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf%20%281%29/builds/4079/steps/system_health.memory_mobile/logs/stdio

Traceback (most recent call last):
  File "/b/rr/tmpAv5thD/w/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 86, in _RunStoryAndProcessErrorIfNeeded
    state.RunStory(results)
  File "/b/rr/tmpAv5thD/w/src/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 "/b/rr/tmpAv5thD/w/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 304, in RunStory
    self._current_page.Run(self)
  File "/b/rr/tmpAv5thD/w/src/third_party/catapult/telemetry/telemetry/page/__init__.py", line 99, in Run
    self.RunPageInteractions(action_runner)
  File "/b/rr/tmpAv5thD/w/src/tools/perf/page_sets/system_health/long_running_stories.py", line 29, in RunPageInteractions
    action_runner.MeasureMemory()
  File "/b/rr/tmpAv5thD/w/src/third_party/catapult/telemetry/telemetry/internal/actions/action_runner.py", line 138, in MeasureMemory
    assert dump_id, 'Unable to obtain memory dump'
AssertionError: Unable to obtain memory dump

INFO:root:Chrome version: None
INFO:root:Try printing formatted exception: None None None

Exception raised when cleaning story run: 

Traceback (most recent call last):
  _RunStoryAndProcessErrorIfNeeded at /b/rr/tmpAv5thD/w/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py:108
    test.DidRunStory(state.platform)
  DidRunStory at /b/rr/tmpAv5thD/w/src/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py:309
    platform.tracing_controller.StopTracing()
  StopTracing at /b/rr/tmpAv5thD/w/src/third_party/catapult/telemetry/telemetry/core/tracing_controller.py:47
    return self._tracing_controller_backend.StopTracing()
  StopTracing at /b/rr/tmpAv5thD/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:108
    self._IssueClockSyncMarker()
  _IssueClockSyncMarker at /b/rr/tmpAv5thD/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:203
    self._RecordIssuerClockSyncMarker)
  RecordClockSyncMarker at /b/rr/tmpAv5thD/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py:193
    sync_id, record_controller_clock_sync_marker_callback)
  _RecordClockSyncMarkerAsyncEvent at /b/rr/tmpAv5thD/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py:170
    'Failed to issue clock sync to devtools client')
ChromeClockSyncError: Failed to issue clock sync to devtools client

Locals:
  has_clock_synced                             : False
  record_controller_clock_sync_marker_callback : <bound method TracingControllerBackend._RecordIssuerClockSyncMarker of <telemetry.internal.platform.tracing_controller_backend.TracingControllerBackend object at 0x7f333fef2590>>
  sync_id                                      : '4003ad60-2517-45c0-85be-8962eb3ab43c'

[  FAILED  ] long_running:tools:gmail-background (141379 ms)