New issue
Advanced search Search tips

Issue 852448 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
tiborg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-VR
Proj-XR



Sign in to add a comment

5%-16.2% regression in xr.browsing.wpr.static at 561297:561370

Project Member Reported by bsheedy@google.com, Jun 13 2018 
Bisect points to https://chromium-review.googlesource.com/1070877, but that doesn't seem right. The metric is extremely noisy while trying to bisect, so I'm not sure if a proper bisect will be feasible.

It does seem like it's returning to the same state it was in about a month ago, so I'm tempted to close as a wontfix.
Project Member

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

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

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


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

pixel_xl

Comment 2 by bsheedy@chromium.org, Jun 13 2018

Components: Internals>VR
Labels: VR-Perf

Comment 3 by tiborg@chromium.org, Jun 20 2018

Cc: tiborg@chromium.org
Labels: FoundIn-69 FoundIn-68
It seems that something has happened. Maybe it makes sense to investigate further.

Comment 4 by bsheedy@chromium.org, Jun 20 2018 

There's actually a similar increase in the same metric in a non-VR benchmark that got ignored https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICQkY37rQkM

Comment 5 by cjgrant@chromium.org, Jun 25 2018

Status: WontFix (was: Untriaged)
Based on Brian's comment, closing this off.

Comment 6 by btebbs@chromium.org, Jul 4

Components: Internals>XR
►

Sign in to add a comment