New issue
Advanced search Search tips

Issue 919920 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jan 9
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

47.7%-51.3% regression in performance_browser_tests at 620345:620442

Project Member Reported by mustaq@chromium.org, Jan 8

Issue description

We have ~20 regressions accompanied by 200+ improvements.  Still filing a bug to notify test owners.



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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=d2397abf69ef76aa2a61e458c8f15ec6e121ca24254abaaaa7303e88f06018f5


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14dd7a3d940000
Cc: crouleau@chromium.org
Owner: m...@chromium.org
Status: WontFix (was: Untriaged)
+crouleau, FYI.

Looks like these are all false alarms because of Justin's recent "fix". The "lower is better" is incorrect because, for A/V sync, we want things closer to zero. In other words, these negative values became less negative, and that's a good thing. :)

I'll have to cut a crbug to fix the A/V sync metric.
Cc: bsheedy@chromium.org
s/Justin/Brian ?

Sign in to add a comment