New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 699051 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

482.7% regression in loading.mobile at 451844:453053

Project Member Reported by kraynov@chromium.org, Mar 7 2017

Issue description

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

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


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

android-nexus5X
Labels: Performance-Loading
 Issue 699054  has been merged into this issue.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Jun 21 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstContentfulPaint_avg/Regular-3G/https___guitar-tuner.appspot.com

Revision             Result                  N
chromium@451843      43213.3 +- 2407.6       21      good
chromium@453053      43266.3 +- 2857.87      21      bad

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 --story-filter=https...guitar.tuner.appspot.com loading.mobile

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

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


| 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 9 by 42576172...@developer.gserviceaccount.com, Jun 21 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstContentfulPaint_avg/Regular-3G/https___guitar-tuner.appspot.com

Revision             Result                  N
chromium@451843      43165.2 +- 2982.37      21      good
chromium@453053      43301.2 +- 1661.57      21      bad

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 --story-filter=https...guitar.tuner.appspot.com loading.mobile

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

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


| 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 10 by 42576172...@developer.gserviceaccount.com, Jun 22 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: 12a3f61803fefb0aeb06f3f4093ea8b06a29fbb3
  bad_revision : 250c4a05efdb4ec893d99ed7fe63236686caec4d

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


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstContentfulPaint_avg/Regular-3G/https___guitar-tuner.appspot.com

Revision             Result                  N
chromium@451843      42902.7 +- 2512.63      21       good
chromium@452451      42972.4 +- 1717.3       14       good
chromium@452770      42841.7 +- 2077.48      14       good
chromium@452911      42948.3 +- 1336.05      14       good
chromium@452979      43131.4 +- 1135.97      14       good
chromium@452980      ---                     ---      build failure
---                  ---                     ---      too many build failures to list
chromium@453053      43406.2 +- 1159.85      14       bad

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 --story-filter=https...guitar.tuner.appspot.com loading.mobile

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

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


| 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 12 by 42576172...@developer.gserviceaccount.com, Jun 22 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstContentfulPaint_avg/Regular-3G/https___guitar-tuner.appspot.com

Revision             Result                  N
chromium@451843      43035.3 +- 2246.91      21      good
chromium@453053      42966.1 +- 1741.48      21      bad

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 --story-filter=https...guitar.tuner.appspot.com loading.mobile

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

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


| 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!
Status: WontFix (was: Untriaged)
the last good revision shows a bad result in bisects.
so this should not be a regression.

Sign in to add a comment