New issue
Advanced search Search tips

Issue 724254 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
perezju@chromium.org
nedngu...@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

52.6% regression in blink_perf.layout at 472411:472426

Project Member Reported by nedngu...@google.com, May 18 2017 
The test cycle time increases by 10 minutes. The temperature of before & after looks comparable. The number of tests are the same. So it's unclear what caused this.

Comment 1 by nedngu...@google.com, May 18 2017 

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmoCavgsM


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

android-webview-nexus6

Comment 3 by perezju@chromium.org, May 19 2017

Cc: perezju@chromium.org
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, May 20 2017 


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

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


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : blink_perf.layout
  Metric       : benchmark_duration/benchmark_duration


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

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979225165028449552

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5584119771168768


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, May 22 2017 


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

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: 1d357b6a46d70097aa28428b1f106284f7fd9990
  bad_revision : 75f368543f24bc196d03e8c657d78f59d4589d42

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


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : blink_perf.layout
  Metric       : benchmark_duration/benchmark_duration
  Change       : 55.16% | 19.0916502363 -> 29.6232855936

Revision             Result                    N
chromium@472410      19.0917 +- 0.136511       6      good
chromium@472412      19.0534 +- 0.0543291      6      good
chromium@472414      29.5651 +- 0.120288       6      bad
chromium@472418      29.6869 +- 0.141241       6      bad
chromium@472426      29.6233 +- 0.141544       6      bad

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

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979091848096440304

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5584119771168768


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 7 by sheriffbot@chromium.org, Jul 14 2017

Labels: Hotlist-Google

Comment 8 by benhenry@google.com, Jan 16

Components: Test>Telemetry

Comment 9 by benhenry@google.com, Jan 16

Components: -Speed>Telemetry
►

Sign in to add a comment