New issue
Advanced search Search tips

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

101.3%-106% regression in page_cycler_v2.basic_oopif at 459676:459679

Project Member Reported by lanwei@chromium.org, Mar 30 2017

Issue description

See the link to graphs below.
 

Comment 1 by lanwei@chromium.org, Mar 30 2017

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7NubowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7K-6qgoM


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

chromium-rel-win10
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 30 2017


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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : page_cycler_v2.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___www.cnn.com

Revision             Result                  N
chromium@459675      2095.22 +- 7651.93      21      good
chromium@459679      2119.72 +- 7149.88      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.cnn.com page_cycler_v2.basic_oopif

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

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


| 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, Apr 11 2017


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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : page_cycler_v2.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___www.cnn.com

Revision             Result                  N
chromium@459675      1819.34 +- 4827.24      21      good
chromium@459679      2159.57 +- 7292.52      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.cnn.com page_cycler_v2.basic_oopif

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

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


| 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)
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