Based on the flakiness dashboard (https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=tracing.tracing_with_background_memory_infra%2Fhttp%3A%2F%2Fwww.bing.com%2F&testType=performance_test_suite), it looks like this story has been failing since it was first enabled. Going to disable it now.

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

commit d51c25550fb162a63ff7462446a6c65760544180
Author: Charlie Andrews <charliea@chromium.org>
Date: Wed Dec 12 00:27:44 2018

Disable bling tracing memory infra story

TBR=crouleau@chromium.org
CC=ssid@chromium.org

Bug: 914092
Change-Id: I57095a320bd561551bbd43025688393199ffbacb
Reviewed-on: https://chromium-review.googlesource.com/c/1372725
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615741}
[modify] https://crrev.com/d51c25550fb162a63ff7462446a6c65760544180/tools/perf/expectations.config

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

commit bea22be5a491464393de99eec4d1239265809489
Author: Caleb Rouleau <crouleau@chromium.org>
Date: Thu Dec 20 19:33:53 2018

Disable tracing benchmark amazon and bing on Windows.

tracing.tracing_with_background_memory_infra/http://www.amazon.com
is flaky on windows. See https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=tracing.tracing_with_background_memory_infra%2Fhttp%3A%2F%2Fwww.amazon.com&testType=performance_test_suite

Bing is also flaky on windows: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=tracing.tracing_with_background_memory_infra%2Fhttp%3A%2F%2Fwww.bing.com%2F&testType=performance_test_suite

THe error is

(ERROR) 2018-12-20 01:29:53,039 page_test_results.Fail:587  Failure recorded: TraceImportError: Unable to select a master clock domain because no path can be found from "TELEMETRY" to "WIN_QPC".
    at ClockSyncManager.ensureAllDomainsAreConnected_ (/tracing/model/clock_sync_manager.html:283:17)
    at ClockSyncManager.selectModelDomainId_ (/tracing/model/clock_sync_manager.html:254:12)
    at ClockSyncManager.getModelTimeTransformer (/tracing/model/clock_sync_manager.html:156:14)
    at TraceEventImporter.toModelTimeFromUs_ (/tracing/extras/importer/trace_event_importer.html:3368:42)
    at TraceEventImporter.processCompleteEvent (/tracing/extras/importer/trace_event_importer.html:586:16)
    at TraceEventImporter.processEvent_ (/tracing/extras/importer/trace_event_importer.html:1245:30)
    at TraceEventImporter.importEvents (/tracing/extras/importer/trace_event_importer.html:1148:16)
    at importer (/tracing/importer/import.html:198:65)
    at task.subTask (/tracing/importer/import.html:145:32)
    at Task.run (/tracing/base/task.html:80:50)

See https://chrome-isolated.appspot.com/browse?namespace=default-gzip&digest=a09f20a96be90a851afcae573b59b2e9c47b55f7&as=tracing.tracing_with_background_memory_infra%5Cbenchmark_log.txt
TBR=charliea@chromium.org
NOTRY=true


Bug: 914092
Change-Id: I1125eaccf4b68863d75b48998f5731330074c169
Reviewed-on: https://chromium-review.googlesource.com/c/1387551
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#618289}
[modify] https://crrev.com/bea22be5a491464393de99eec4d1239265809489/tools/perf/expectations.config