I noticed that the run time for browser_tests on our bare-metal bots in chromium.webrtc[.fyi] is taking >1 hour to run. This grows the blame list and makes the testers unable to catch up with pending builds.
I think there's some low hanging fruit here since some of the tests matched in the current filter already run in the main Chromium bots (on VMs) and doesn't provide any extra value when run on a real machine (with audio and video devices).
Currently the flags of interest are:
--gtest_filter=WebRtc*:Webrtc*:TabCapture*:*MediaStream* --run-manual
See https://docs.google.com/document/d/1DzOkzorCkEhGMqvvkdufIwPmUlOZoDkcRuH5_bvT-Vw/edit for discussion on which tests to filter and how.
Comment 1 by bugdroid1@chromium.org
, Apr 11 2017