All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=597714

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0PvboAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0LaTqgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0JyNvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0OOloQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0LbKvQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0LbKvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgkKGwzwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0JWRtwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgkIH11AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0Oz5owsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgkOL_kgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0Oz5owkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0JWRtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0Oy3qwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0JHwsQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0La0rAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgkKGwzwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0JXGpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgkNuovQoM


Bot(s) for this bug's original alert(s):

webrtc-linux-large-tests
webrtc-win-large-tests

r12093 == https://codereview.webrtc.org/1757683002

skvlad@, can you confirm that these improvements are expected?

This issue shares the same root cause with https://bugs.chromium.org/p/chromium/issues/detail?id=597332. After the change, RTCPSender::SetRTCPStatus gets called an extra time, which reschedules the next RTCP packet to be 400 ms later than originally planned. This changes the timing of the entire test.