New issue
Advanced search Search tips

Issue 854664 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-XR
Proj-XR-VR



Sign in to add a comment

2.4%-3.9% regression in xr.browsing.wpr.static at 560469:560718

Project Member Reported by bsheedy@google.com, Jun 20 2018

Issue description

Bisect points to https://chromium-review.googlesource.com/1068097.

I think at this point we should just rename the vr_perf_tests target to michael_cl_detector_tests.

The bisect test results were remarkably stable for a reported_by_os metric, but this causing an issue makes absolutely no sense. Given that there aren't any other VR-related changes in the regression range, probably a WontFix.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 20 2018

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

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


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

pixel_xl
Components: UI>Browser>VR
Labels: Proj-VR VR-Perf
Cc: billorr@chromium.org
Status: WontFix (was: Assigned)
IF reviewer:mthiesse OR owner:mthiesse THEN REGRESSION

In any case, that's Bill's change not mine.

I'm going to WontFix, because that's absurd and even if that caused a regression I'm not going to fix it :P
Woops, I saw "mthiesse" in the commit message and assumed you were the author, not the reviewer.

Sign in to add a comment