New issue
Advanced search Search tips

Issue 781242 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
mustaq@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10%-798.1% regression in blink_perf.layout at 512747:512979

Project Member Reported by mustaq@chromium.org, Nov 3 2017 
This is a big regression:
- big in regression magnitude (upto ~800%),
- big in number of metrices affected (150+).
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 3 2017 

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

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


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

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2
android-one
android-webview-nexus5X
android-webview-nexus6
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 3 2017 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : blink_perf.layout
  Metric       : long-line-nowrap-collapse/long-line-nowrap-collapse


Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.layout

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8963937244491465008


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Nov 4 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 2a3981b3710692cf94e6b5ded85cdc30370b2f47
  bad_revision : 8502b9514b78dfd69c4d9c02214c44cdae1b5353

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : blink_perf.layout
  Metric       : long-line-nowrap-spans-collapse/long-line-nowrap-spans-collapse

Revision             Result                  N
chromium@512798      213.943 +- 11.4452      6      good
chromium@512821      216.269 +- 3.71153      6      good
chromium@512824      207.524 +- 4.49106      6      good
chromium@512826      1168.49 +- 52.4661      6      bad
chromium@512827      1173.12 +- 41.7002      6      bad
chromium@512833      1162.3 +- 28.6681       6      bad
chromium@512844      1166.82 +- 27.652       6      bad
chromium@512889      1170.04 +- 24.6377      6      bad
chromium@512979      1166.54 +- 25.7546      6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.layout

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8963937266180138976


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Nov 4 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 2a3981b3710692cf94e6b5ded85cdc30370b2f47
  bad_revision : 8502b9514b78dfd69c4d9c02214c44cdae1b5353

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : blink_perf.layout
  Metric       : latin-complex-text/latin-complex-text

Revision             Result                  N
chromium@512798      72.7583 +- 1.82323      6      good
chromium@512821      72.3097 +- 2.17919      6      good
chromium@512824      72.0672 +- 1.97959      6      good
chromium@512826      668.058 +- 15.0053      6      bad
chromium@512827      675.485 +- 25.9447      6      bad
chromium@512833      672.674 +- 23.5562      6      bad
chromium@512844      667.917 +- 11.9438      6      bad
chromium@512889      665.925 +- 11.3847      6      bad
chromium@512979      685.158 +- 20.5821      6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.layout

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8963937594016174512


For feedback, file a bug with component Speed>Bisection

Comment 8 by mustaq@chromium.org, Jan 9 2018

Status: WontFix (was: Untriaged)
Seems the regressions were fixed soon afterwards.  I check a random sample of 20 out of 156 tests.
►

Sign in to add a comment