Actually I'm not seeing any data on the perf dashboard for this test on win-10-perf. But it does have at least one successful run:

https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/win-10-perf/1219

I can't access the dashboard logs for that run: https://logs.chromium.org/v/?s=chrome%2Fbuildbucket%2Fcr-buildbucket.appspot.com%2F8929750965704325168%2F%2B%2FResults_Dashboard__2c05f15b-d2f6-430a-beaa-f846c85b42e7

Ned, Emily, any ideas what's going on here?

You are talking about performance_browser_tests correct, not components_perftests?  components_perftests is passing. 

It looks like there is some data for this test in the dashboard: 

https://chromeperf.appspot.com/report?sid=a39f7714b0cb86fb8954b61919df9505e8fdfecd604eb5cffe7ca7dec3abce6d

It appears to be failing some of the tests, but we are still uploading data for the rest of them (at the bottom of the output you can see the successful upload https://logs.chromium.org/logs/chrome/buildbucket/cr-buildbucket.appspot.com/8929750965704325168/+/steps/performance_browser_tests_on_Intel_GPU_on_Windows_on_Windows-10/0/stdout)


Logs to the failing test: 
https://chrome-swarming.appspot.com/task?id=41327fb106772a10&refresh=10&show_raw=1

[14/14] TabCapturePerformanceTest.Performance/3 (21443 ms)

1 test failed:

    CastV2PerformanceTest.Performance/2 (../../chrome/browser/extensions/api/cast_streaming/performance_test.cc:698)

1 test timed out:

    CastV2PerformanceTest.Performance/0 (../../chrome/browser/extensions/api/cast_streaming/performance_test.cc:698)

1 test crashed:

    CastV2PerformanceTest.Performance/1 (../../chrome/browser/extensions/api/cast_streaming/performance_test.cc:698)

Command ['.\\performance_browser_tests.exe', '--test-launcher-print-test-stdio=always', '--test-launcher-timeout=120000', '--gtest_filter=TabCapturePerformanceTest.*:CastV2PerformanceTest.*', '--test-launcher-jobs=1', '--enable-gpu', '--verbose'] returned exit code 1

+miu@ as the owner of performance_browser_tests to see if they can identify the test failure.

So many things wrong on the windows bots it's hard to ensure all the bugs are filed :(

components_perftests fails most of the time: https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/win-10-perf

Should I file a separate bug for that? Or could there be some same root cause?

The ProtoDBPerfTest look like they are hanging. This is being tracked in issue 879922 as far as I can tell.

Observations:

1. All tests seem to pass just fine on retry. There's some kind of weirdness where either/both: a) the compositor is not generating any frames; b) trace event data is not making it back to the test code for analysis.

2. The test that TIMED_OUT was not due to broken test code: There is is a log line at the start of the first CastV2PerformanceTest.Performance/0 run with a timestamp of 16:41:16. Then, the very first "Started tab capture" console log message from the web page part of the test code has a timestamp of 16:41:31. So, 15 seconds goes by at start-up where nothing happens?!?

As I can't seem to replicate anything on my local Windows 10 machine, I'll try adding some extra logging to performance_browser_tests to try to root-cause what's going on in the bot...

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

commit fc50c1477673ff62ae6243ab30de31fd4b430c01
Author: Yuri Wiitala <miu@chromium.org>
Date: Tue Nov 20 01:17:28 2018

performance_browser_tests: Add temporary logging to RCR freezes.

TBR=sullivan@chromium.org

Bug:  906656 
Change-Id: I6eb1c8604b8dc6307fde4df09bfbe7c2918aeb8a
Reviewed-on: https://chromium-review.googlesource.com/c/1343062
Reviewed-by: Yuri Wiitala <miu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609542}
[modify] https://crrev.com/fc50c1477673ff62ae6243ab30de31fd4b430c01/chrome/browser/extensions/api/cast_streaming/performance_test.cc
[modify] https://crrev.com/fc50c1477673ff62ae6243ab30de31fd4b430c01/chrome/test/data/extensions/api_test/cast_streaming/performance.js