New issue
Advanced search Search tips

Issue 725157 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

89.8% regression in loading.mobile at 472225:472383

Project Member Reported by benhenry@google.com, May 22 2017

Issue description

Very noisy.
 
Project Member

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


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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstContentfulPaint_avg/Regular-3G/https___dev.opera.com_

Revision             Result                  N
chromium@472224      8473.17 +- 3909.0       20      good
chromium@472383      8191.67 +- 201.516      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...dev.opera.com. loading.mobile

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

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


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


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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstContentfulPaint_avg/Regular-3G/https___dev.opera.com_

Revision             Result                  N
chromium@472224      4527.35 +- 1492.85      21      good
chromium@472383      4562.43 +- 3275.0       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...dev.opera.com. loading.mobile

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

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


| 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!
There used to be a bisect mode that checked the std dev, but that seems to have been removed.  I doubt the bots will reliable find the regression here :(
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Jun 12 2017


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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstContentfulPaint_avg/Regular-3G/https___andreasbovens.github.io_inbox-attack_

Revision             Result                  N
chromium@471000      4699.54 +- 2536.58      21      good
chromium@472383      4713.02 +- 1572.32      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...andreasbovens.github.io.inbox.attack. loading.mobile

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

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


| 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 13 2017


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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstContentfulPaint_avg/Regular-3G/https___andreasbovens.github.io_inbox-attack_

Revision             Result                  N
chromium@471000      4619.75 +- 1061.04      21      good
chromium@472383      4585.65 +- 1421.09      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...andreasbovens.github.io.inbox.attack. loading.mobile

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

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


| 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 11 by sheriffbot@chromium.org, Jul 14 2017

Labels: Hotlist-Google
Status: WontFix (was: Untriaged)
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. 

Sign in to add a comment