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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoMixtwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwOvqvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwLK1tQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoLThqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoJLtvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwKHnrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwOuQtQoM


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

webrtc-android-tests-nexus72
webrtc-mac-large-tests
webrtc-win-large-tests

It seems like there are some regressions in several screenshare related stats, and an improvement in PSNR. It looks like this CL may be responsible: https://codereview.webrtc.org/1757313002 
Could you have a look to see if this is expected? Thanks!

 Issue 594578  has been merged into this issue.

Don't think these are too scary and I believe they are changes in how we measure overuse, I'll close as WontFix since I don't have anything immediately actionable. :)