New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 804329 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
█ pmeenan@chromium.org
tbansal@chromium.org
mmenke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

308.4% regression in smoothness.tough_canvas_cases at 530688:530717

Project Member Reported by pmeenan@chromium.org, Jan 22 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 22 2018 

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

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


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

android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 22 2018

Cc: mmenke@chromium.org tbansal@chromium.org
Owner: tbansal@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12ec3ca4840000

Update net adaptive proxy timeout experiment logic
By tbansal@chromium.org · Sat Jan 20 01:16:39 2018
chromium @ 162eabe5e3f653d03d26a22aaefd5ba02df59dd2

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jan 22 2018 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14e63e98840000

Comment 6 by tbansal@chromium.org, Jan 22 2018

Owner: ----
Status: (was: Assigned)
I do not think this is related to my CL.  Also, the regression is not reproducible (see #5 above).

Comment 7 by pmeenan@chromium.org, Jan 23 2018

Status: WontFix
Looks like an infrastructure change.  The ref build stopped producing data at the same point that the metric shifted.  Sorry about the false alarm.
►

Sign in to add a comment