New issue
Advanced search Search tips

Issue 808613 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
flackr@chromium.org
kouhei@chromium.org
npm@chromium.org
hferre...@igalia.com
ksakamoto@chromium.org
dpranke@chromium.org
nedngu...@google.com
alancutter@chromium.org
aga...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.3%-9.4% regression in system_health.common_mobile at 531416:531494

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 2 2018 

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

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


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

android-nexus5
android-nexus6
chromium-rel-mac11-pro
Project Member

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

Cc: depot-tools-roller@chromium.org flackr@chromium.org alancutter@chromium.org
Owner: depot-tools-roller@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/148a8d4e840000

Add smcgruer as an animations OWNER by flackr@chromium.org
chromium @ b091c264862d26ac12d932e84eef7bd5f674e62b

Roll src/third_party/depot_tools/ 0f7b2007a..fd4ad2416 (1 commit) by depot-tools-roller@chromium.org
chromium @ 14fc99e3fd3614096caab7c7a8362edde8327a5d

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 4 by npm@chromium.org, Feb 6 2018

Cc: -depot-tools-roller@chromium.org dpranke@chromium.org hferre...@igalia.com aga...@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
Only 1 commit from depot_tools roller:
https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/842402
Project Member

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

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

Comment 8 by 42576172...@developer.gserviceaccount.com, Feb 8 2018 

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

Comment 9 by sullivan@chromium.org, Feb 14 2018 

Looks like the test failed many times in the bisect in #3, 100% of the time in #6, and almost-but-not-quite reproed in #8. Trying another bisect on N5.
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Feb 14 2018

Cc: nedngu...@google.com ksakamoto@chromium.org kouhei@chromium.org
Owner: ksakamoto@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12e96643840000

Re-record loading.desktop story set by ksakamoto@chromium.org
https://chromium.googlesource.com/chromium/src/+/ea8b932d3e0df99e89dc606dc35335d10e414c94

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 12 by ksakamoto@chromium.org, Feb 15 2018

Owner: ----
Status: Untriaged (was: Assigned)
For loading.desktop, regression is due to re-recording (WontFix). I'm not sure for system_health.common_mobile - my CL doesn't really look like a curplit?
Project Member

Comment 14 by 42576172...@developer.gserviceaccount.com, Feb 15 2018 

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

Comment 15 by nednguyen@chromium.org, Feb 15 2018

Status: WontFix (was: Untriaged)
Probably the dip in the graph is just noise. The "regression" doesn't make it worse than before the dip. So I mark this WontFix
►

Sign in to add a comment