New issue
Advanced search Search tips

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

11.2% improvement in system_health.common_desktop at 463683:463928

Project Member Reported by samans@chromium.org, Apr 26 2017

Issue description

See the link to graphs below.
 

Comment 1 by samans@chromium.org, Apr 26 2017

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

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


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

chromium-rel-mac11-pro
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 26 2017


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

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/load_social/load_social_vk

Revision             Result                  N
chromium@463682      503.345 +- 235.859      21      good
chromium@463928      490.965 +- 208.096      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.social.vk system_health.common_desktop

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

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


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


=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/load_social/load_social_vk

Revision             Result                  N
chromium@463682      553.891 +- 288.303      21      good
chromium@463805      526.639 +- 171.972      21      unknown
chromium@463928      516.385 +- 364.313      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.social.vk system_health.common_desktop

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

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


| 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