Fix WebRTC tests running on Swarming but not implementing --isolated-script-test-output flag. |
|||
Issue descriptionI had to revert https://chromium-review.googlesource.com/c/472290/ today after breaking our tree. It's because we have two tests that aren't using https://chromium.googlesource.com/external/webrtc/+/master/tools-webrtc/gtest-parallel-wrapper.py, which means when the recipe code passes --isolated-script-test-output to the tests and no JSON is output, the test counts as a failure.
,
Apr 10 2017
I haven't had time to dig into the details, but it has worked as intended for us so far. The tests in question for WebRTC are: low_bandwidth_audio test and webrtc_nonparallel_tests. Example failure of webrtc_nonparallel_tests: https://build.chromium.org/p/client.webrtc/builders/Win32%20Debug/builds/12458
,
Apr 12 2017
This was fixed by https://codereview.webrtc.org/2806373002/ (I forgot to add the chromium: prefix in the BUG= entry). |
|||
►
Sign in to add a comment |
|||
Comment 1 by tansell@chromium.org
, Apr 10 2017