Make sure all WebRTC tests use gtest-parallel script |
||
Issue descriptionIn order to benefit from the recently added gtest-parallel script's retry capabilities ( issue 718339 ), we should make sure all our tests use it, even if they don't run in parallel. Running in a single thread can be accomplished by passing --workers=1 to gtest-parallel. Preferably the script should output the logs similar to how running the test without the wrapper in this special case. Tests that are currently not using gtest-parallel are running on the bare-metal bots. I suggest we should migrate the following: * video_capture_tests * voe_auto_test Doing that will also enable us gathering flakiness data for them, right?
,
May 9 2017
More work = a step in the buildbot that uploads the tests to the test-results app
,
Sep 21 2017
Is this now completed?
,
Sep 21 2017
All tests are using gtest-parallel except gradle_project_test and perf tests (webrtc_perf_tests, low_bandwidth_audio_test and video_quality_loopback_test)
,
Sep 21 2017
And I assume we don't want to change those? If so, please close this.
,
Sep 22 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by ehmaldonado@chromium.org
, May 9 2017