commit | 33b8c034b1911e390d16225528e5a2aabdbae625 | [log] [tgz] |
---|---|---|
author | Mirko Bonadei <mbonadei@webrtc.org> | Tue Jul 22 13:31:34 2025 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 23 06:50:38 2025 |
tree | f64f691b768e249621362378028470e3fe9473f1 | |
parent | 3bb0bd9f3678a79eae987ea8b033a202cb9ccbe7 [diff] |
Reland "Allow StdoutMetricsExporter to merge stream and peers info in test_name." This is a reland of commit 772386c50321aabfcaeea75857515d6f939c6ac1 Original change's description: > Allow StdoutMetricsExporter to merge stream and peers info in test_name. > > Currently, metrics printed by StdoutMetricsExporter have lost info > about stream, sender/receiver and peers. They look like: > > RESULT psnr_dB: foreman_cif_net_delay_0_0_plr_0_VP9= {38.697086,1.7471016} unitless_biggerIsBetter > > Which makes it impossible to know the stream to which this PSNR > measurement was referring to. > > This CL tries to restore the behaviour before [1], which changed test > names with: > > std::string DefaultVideoQualityAnalyzer::GetTestCaseName( > const std::string& stream_label) const { > if (!absl::GetFlag(FLAGS_isolated_script_test_perf_output).empty()) { > return test_label_ + "/" + stream_label; > } > return test_label_; > } > > [1] - https://webrtc-review.googlesource.com/c/src/+/383720 > > Bug: None > Change-Id: Iad3cf5cb723e37c2a32fc510a2d484b796024ace > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/399280 > Reviewed-by: Jeremy Leconte <jleconte@google.com> > Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#45185} Bug: b/433477101 Change-Id: I8c6bf97835c98ae683a17554e0eecdf44c62c3df Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/401560 Reviewed-by: Jeremy Leconte <jleconte@google.com> Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/main@{#45200}
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.