New issue
Advanced search Search tips

Issue 640370 link

Starred by 1 user
Status: WontFix
Owner:
nisse@chromium.org
Closed: Aug 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

34.9% improvement in browser_tests at 413437:413439

Project Member Reported by peah@chromium.org, Aug 23 2016 
nisse@: It seems like this may be caused by your CL ttps://codereview.chromium.org/2263183002. Could you please take a look!

Comment 1 by peah@chromium.org, Aug 23 2016 

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg3onDoAkM


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

chromium-webrtc-trunk-tot-rel-mac

Comment 2 by nisse@chromium.org, Aug 24 2016 

I think this (and related alerts) are as expected. The cl reverts my change from a few days ago, which produced bogus timestamps on captured frames. Anything in particular you want me to look at?

Comment 3 by peah@chromium.org, Aug 24 2016 

Great! No, I was mainly wanting you to have a look to see whether it would make sense that these regressions are related to your CL.

Comment 4 by peah@chromium.org, Aug 31 2016

Status: WontFix (was: Assigned)
As it looks as if these are expected, I'll close this issue.
►

Sign in to add a comment