Issue 788792 link

Starred by 1 user

Issue metadata

Status:	WontFix
Owner:	gurcheta...@chromium.org
Closed:	Nov 2017
Cc:	ihf@chromium.org
EstimatedDays:	----
NextAction:	----
OS:	----
Pri:	2
Type:	Bug-Regression
Gfx-Guard

34.1% regression in graphics_GLMark2 at 32620021011300000:32640001011600000

Project Member Reported by gurchetansingh@google.com, Nov 27 2017

Issue description

ChromeOS Version range: 64.10113.0.0 - 64.10116.0.0 
Chrome Version range: 64.0.3262.2 - 64.0.3264.0 

https://crosland.corp.google.com/log/10113.0.0..10116.0.0
https://chromium.googlesource.com/chromium/src/+log/64.0.3262.0..64.0.3264.0?pretty=fuller&n=10000

Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 27 2017

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

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


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

cros-zako

Comment 2 by gurcheta...@chromium.org, Nov 27 2017

Labels: Gfx-Guard

Comment 3 by gurcheta...@chromium.org, Nov 30 2017

Status: WontFix (was: Assigned)

As per ihf@, we don't care about graphics_GLMark2 micro-benchmark regressions (though we should worry if the aggregate score regresses).  graphics_GLMark2 mostly checks for correctness, not performance.

►

Issue 788792 link

Issue metadata

34.1% regression in graphics_GLMark2 at 32620021011300000:32640001011600000

Issue description

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 27 2017

Comment 1 Deleted

Comment 2 by gurcheta...@chromium.org, Nov 27 2017

Comment 2 Deleted

Comment 3 by gurcheta...@chromium.org, Nov 30 2017

Comment 3 Deleted

Sign in to add a comment