Björn Terelius ff58aed678 Process events with the same timestamp in a defined order. ... As before, events are processed primarily in timestamp order. This CL adds a heuristic to break ties for events with the same timestamp. - Roughly speaking, configs and connectivity events are processed first, followed by incoming packets, then BWE updates, then other (general) events and finally outgoing packets and ALR events. - Among RTP packets, transport sequence number is used to break ties. - The insertion order (into the EventProcessor) is used as a last resort. Bug: b/282153758 Change-Id: I914e4500ca63e1a8754766d1833a7b32f6a38176 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/308140 Commit-Queue: Björn Terelius <terelius@webrtc.org> Reviewed-by: Per Kjellander <perkj@webrtc.org> Cr-Commit-Position: refs/heads/main@{#40318}		2023-06-20 14:21:17 +00:00
..
g3doc	Reland "Migrate WebRTC documentation to new renderer"	2023-01-31 09:30:04 +00:00
rtc_event_log	Process events with the same timestamp in a defined order.	2023-06-20 14:21:17 +00:00
BUILD.gn	Process events with the same timestamp in a defined order.	2023-06-20 14:21:17 +00:00
OWNERS	Removing skvlad@ from logging/OWNERS.	2018-02-02 13:03:29 +00:00