New issue
Advanced search Search tips

Issue 810022 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

24.3% regression in loading.mobile at 534666:534683

Project Member Reported by chiniforooshan@chromium.org, Feb 7 2018

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=810022

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


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

android-nexus5X
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14b45e89840000
Some of the graphs have went down to original values, some are still up. Rerunning on a different story.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Feb 12 2018

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/12fed6b5840000
Pinpoint error is already reported in catapult:4243.
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Mar 13 2018

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14c3bf8e440000
Project Member

Comment 12 by 42576172...@developer.gserviceaccount.com, Mar 13 2018

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14eaa71e440000
Project Member

Comment 13 by 42576172...@developer.gserviceaccount.com, Mar 13 2018

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/11916916440000
Cc: dtu@chromium.org sullivan@chromium.org
+dtu, will we be able to bisect once it's possible to bisect with a patch?

Comment 15 by dtu@chromium.org, Mar 20 2018

Yes, I think that's possible.
Project Member

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

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/12fce38b440000
Kicked off a few more bisects with https://chromium-review.googlesource.com/c/chromium/src/+/922581 pinned now that this is possible on pinpoint.
Project Member

Comment 21 by 42576172...@developer.gserviceaccount.com, May 31 2018

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

All of the attempts failed. See the individual attempts for details on each error.
Project Member

Comment 22 by 42576172...@developer.gserviceaccount.com, May 31 2018

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

All of the attempts failed. See the individual attempts for details on each error.
dtu: This broke because pinned CL only works for the entire bisect, not a partial bisect, right? Is that planned?

Comment 24 by dtu@chromium.org, May 31 2018

The builds show this error message:

MBErr: Builder name "Android Compile Perf"  not found under masters[tryserver.chromium.perf] in "/b/c/b/Android_Compile_Perf/src/tools/mb/mb_config.pyl"

So this failed because the builder names changed. We would need to patch in the builder config changes as well. But we don't support multiple patches. (issue 820653)
Status: WontFix (was: Untriaged)
THis can't be bisected.

Sign in to add a comment