New issue
Advanced search Search tips

Issue 794665 link

Starred by 1 user
Status: Fixed
Owner:
jmad...@chromium.org
Closed: Jan 2018
Cc:
simonhatch@chromium.org
dtu@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue angleproject:1390



Sign in to add a comment

4.5%-10.1% regression in angle_perftests at 522925:522980

Project Member Reported by jmadill@google.com, Dec 13 2017 
The was likely a regression from the revert of a dirty bits patch.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 13 2017 

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

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


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

chromium-rel-win7-gpu-nvidia

Comment 3 by jmad...@chromium.org, Dec 13 2017

Blocking: angleproject:1390
Cc: -jmadill@google.com
Components: Internals>GPU>ANGLE
Owner: jmad...@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Dec 13 2017 

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

Comment 5 by jmad...@chromium.org, Jan 3 2018

Cc: simonhatch@chromium.org
Status: Fixed (was: Assigned)
Bisect was a bit odd. But graph has recovered.

Comment 6 by simonhatch@chromium.org, Jan 3 2018

Cc: dtu@chromium.org
+dtu Dave any idea what happened here?

Comment 7 by dtu@chromium.org, Jan 3 2018 

The p-value for the last two points is 0.140465048158.
I upped the p-value cutoff from 0.1 to 0.2 in https://chromium-review.googlesource.com/c/catapult/+/823225, which landed 12/14. This bisect ran on 12/13, one day too early :)

Comment 8 by jmad...@chromium.org, Jan 3 2018 

Sounds fine. Thanks for following up Simon/Dave.
►

Sign in to add a comment