Also applies to PPAPINaClNewlibTest.MediaStreamVideoTrack:
[104/104] PPAPINaClPNaClTest.MediaStreamVideoTrack (TIMED OUT)
2 tests timed out:
    PPAPINaClNewlibTest.MediaStreamVideoTrack (e:\b\build\slave\win_builder\build\src\chrome\test\ppapi\ppapi_browsertest.cc:1159)
    PPAPINaClPNaClTest.MediaStreamVideoTrack (e:\b\build\slave\win_builder\build\src\chrome\test\ppapi\ppapi_browsertest.cc:1159)

I found several interesting facts about this issue.
 * Only two builds failed because this timeout in 200 builds (https://build.chromium.org/p/chromium.webrtc.fyi/builders/Win10%20Tester?numbuilds=200)
 * Those two failed builds are webrtc related (project is webrtc).

 * I opened several successful builds. All of their MediaStreamVideoTrack tests are passed in the first run (no retry. Looks like if one MediaStreamVideoTrack test failed, all tests failed, retry didn't fix the problem).

So I guess probably this flaky is because of some webrtc environment related issue. (Looks like JS [1] cannot open the media stream video track).

[1] https://code.google.com/p/chromium/codesearch#chromium/src/ppapi/tests/test_media_stream_video_track.cc&rcl=1464678978&l=27

See it again https://build.chromium.org/p/chromium.webrtc.fyi/builders/Win10%20Tester/builds/3027/steps/browser_tests/logs/stdio

+emircan

There are a lot of errors of "Failed to reserve i420 output buffer". What does it mean? Maybe it is related to the flaky.

[3648:5600:0614/053238:ERROR:video_capture_device_client.cc(142)] Failed to reserve I420 output buffer.
[3648:5600:0614/053238:ERROR:video_capture_device_client.cc(142)] Failed to reserve I420 output buffer.
[3648:5600:0614/053238:ERROR:video_capture_device_client.cc(142)] Failed to reserve I420 output buffer.
[3648:5600:0614/053238:ERROR:video_capture_device_client.cc(142)] Failed to reserve I420 output buffer.
[3648:5600:0614/053238:ERROR:video_capture_device_client.cc(142)] Failed to reserve I420 output buffer.

The number of buffers in the capture pipeline is limited, namely 3.
https://cs.chromium.org/chromium/src/content/browser/renderer_host/media/video_capture_manager.cc?rcl=0&l=96
When other agents are holding onto buffers, we don't have any buffer to capture into, and this message comes. I hope that helps tracking what might be wrong.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

There has been a lot of refactor around video_capture_device_client.cc code. I think this is no longer applicable.