These tests often fail in 'ExtrapolateLocalTime' because the result gives a negative Timestamp. Here is the stack from https://chromium-swarm.appspot.com/task?id=6173230e67897b10: PC: @ 0x7f03afdb8e87 (unknown) raise ... @ 0x55f4a360ba71 352 webrtc::Timestamp::operator+() @ 0x55f4a47ecaf3 160 webrtc::TimestampExtrapolator::ExtrapolateLocalTime() Low-Coverage-Reason: coverage isn't that low. Change-Id: If3e7cbf31d6c4800727b24352ed2c6edc425fc73 Bug: webrtc:15022 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/300600 Reviewed-by: Henrik Boström <hbos@webrtc.org> Reviewed-by: Rasmus Brandt <brandtr@webrtc.org> Commit-Queue: Jeremy Leconte <jleconte@google.com> Cr-Commit-Position: refs/heads/main@{#39853}