New issue
Advanced search Search tips

Issue 893870 link

Starred by 1 user
Status: Assigned
Owner:
dtu@chromium.org
Cc:
simonhatch@chromium.org
wolenetz@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on: View detail
issue 894529
issue 894549


Sign in to add a comment

17.7% regression in media.mobile at 597380:597398

Project Member Reported by wolenetz@chromium.org, Oct 9 
This alert looks valid, though more recently its trace has *more* than recovered (better than before the alert).

Doing a bisect to help inform regression culprit owner of this (though the regression itself might already have been fixed).
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 9 

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

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


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

Android Nexus5 Perf

media.mobile - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 10 

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

Comment 5 by wolenetz@chromium.org, Oct 10 

Since this has similar trace behavior to  bug 893868 , I'll widen the bisect range and retry...

Comment 6 by wolenetz@chromium.org, Oct 11

Blockedon: 894549

Comment 7 by wolenetz@chromium.org, Oct 11

Blockedon: 894529
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Oct 12 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/13684c0ae40000
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Oct 13 

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

Comment 11 by wolenetz@chromium.org, Nov 6

Cc: simonhatch@chromium.org
Components: Speed>Bisection
Owner: dtu@chromium.org
Getting a bisection on a wider range is still blocked on bug 894529. --> dtu@ and cc+simonhatch@ for visibility and assistance obtaining a successful bisection.

This bug in particular is lower priority since the trace, when I filed this bug, had already recovered more than the regression.

Comment 12 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment