New issue
Advanced search Search tips

Issue 826801 link

Starred by 1 user
Status: WontFix
Owner:
ksakamoto@chromium.org
Closed: Jul 12
Cc:
npm@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.6% regression in loading.desktop at 540769:541069

Project Member Reported by npm@chromium.org, Mar 28 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 28 2018 

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

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


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

chromium-rel-mac11-pro
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 28 2018 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/11dfebeb440000

Comment 4 by npm@chromium.org, Mar 28 2018

Owner: ksakamoto@chromium.org
Status: Assigned (was: Untriaged)
Looking at the previous regression in the graph, maybe this is also related ksakamoto@? I'm not sure if there were any additional CLs for story set re-recording after the first one.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Mar 28 2018 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/149c1c97440000

Comment 7 by ksakamoto@chromium.org, Mar 29 2018 

Yeah, the jump on Feb 5 must be the story set re-recording. I'm not sure for the second one around Mar 6.

Comment 8 by ksakamoto@chromium.org, Jul 12

Status: WontFix (was: Assigned)
QQ_cold got recovered from the regression since Mar 6. Let's close this.
►

Sign in to add a comment