| commit | d2637a3436ea8b0e8122af6029b6964e393cb4e4 | [log] [tgz] |
|---|---|---|
| author | Mirko Bonadei <mbonadei@webrtc.org> | Fri Dec 24 10:27:55 2021 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Dec 30 19:43:39 2021 |
| tree | 86332c37fd8abe4c26bab6eff4bed62ce4cb407f | |
| parent | d77b5924c83256e5731f33b06a0003d30cfefcc5 [diff] |
Remove dependency on std::sort implementation detail. When adding samples to the counter in the test body, most of them get added at the same time (rtc::TimeMicros()). This means that the comparator [2] is not able to sort them explicitly (for the comparator they are equal). PerfTest.TestGetPerfResultsHistogramsWithStatsCounter was relying on std::sort implementation being stable, but it is not. If stability is needed, std::stable_sort should be used so this CL switches ::webrtc::test:GetSortedSamples() to std::stable_sort. [1] - https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/api/numerics/samples_stats_counter.cc;l=31;drc=9d777620236ec76754cfce19f6e82dd18e52d22c [2] - https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/test/testsupport/perf_test.cc;l=51-55;drc=a2e3d80cf6f8833ec6f2c5f8e69c2a58a52ddd62 Bug: None Change-Id: I99a44720ce3ad577f0cdb42aa633bd73d62aeaff Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/242961 Reviewed-by: Tomas Gunnarsson <tommi@webrtc.org> Commit-Queue: Tomas Gunnarsson <tommi@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35600}
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.