Issue metadata
Sign in to add a comment
|
ProcessMemoryMetricsEmitterTest.FetchDuringTrace fail in official builds. |
||||||||||||||||||||
Issue descriptionTest output: [ RUN ] ProcessMemoryMetricsEmitterTest.FetchDuringTrace ../../chrome/browser/metrics/process_memory_metrics_emitter_browsertest.cc(165): error: Expected: (sources.size()) >= (count), actual: 0 vs 1 Expected at least 1 renderers with url: about:blank This is failing on the pinned and tot win clang bots: https://build.chromium.org/p/chromium.fyi/builders/CrWinClang64%20tester/builds/6574 https://build.chromium.org/p/chromium.fyi/builders/ClangToTWin%20tester/builds/8379 These failures started after this CL: https://chromium-review.googlesource.com/596270
,
Aug 15 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by thakis@chromium.org
, Aug 11 2017Summary: ProcessMemoryMetricsEmitterTest.FetchDuringTrace fail in official builds. (was: ProcessMemoryMetricsEmitterTest.FetchDuringTrace test failing on WinClang bots)