commit | 7a5978e4cd914c7298133eac08e2fbc57d18c562 | [log] [tgz] |
---|---|---|
author | Jeremy Leconte <jleconte@google.com> | Tue Feb 22 07:26:33 2022 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 22 07:57:34 2022 |
tree | a8452393b1424a589f2759ff93e64a3d1af6259b | |
parent | 694eae7064b6b53162e6a8084366dfb5618677bd [diff] |
Revert "Add the possibility to output a json gtest output to the perf tests." This reverts commit cbfa235b3548ae1a0b8f5b80a879214ca5f1bd56. Reason for revert: iOS bots will use flags_compatibility with isolated_script_test_output but not gtest_output. Original change's description: > Add the possibility to output a json gtest output to the perf tests. > > We use the Chromium existing flag isolated_script_test_output that we translate into gtest_output. > This is because the Chromium flag has the same purpose as gtest_output and is already provided in the recipe modules. > > No-Presubmit: True > Bug: b/197492097 > Change-Id: Ia432a85b0e0ab32008b39ffe751d11aefb9b24ea > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/251041 > Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> > Commit-Queue: Jeremy Leconte <jleconte@google.com> > Cr-Commit-Position: refs/heads/main@{#35937} No-Presubmit: True Bug: b/197492097 Change-Id: I94e75328570f89011fbb0daf035f0072b8ea2f7d Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/252040 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Jeremy Leconte <jleconte@google.com> Cr-Commit-Position: refs/heads/main@{#36042}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.