New issue
Advanced search Search tips

Issue 703154 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

54.7%-231.2% regression in system_health.common_desktop at 456933:457255

Project Member Reported by tdres...@chromium.org, Mar 20 2017

Issue description

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjMq2-QkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjO_sugoM


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

android-webview-nexus6
linux-release
Project Member

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


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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/browse_search/browse_search_google

Revision             Result                  N
chromium@457143      438.272 +- 368.994      21      good
chromium@457241      429.943 +- 273.544      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=browse.search.google system_health.common_desktop

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

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


| 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, Mar 20 2017


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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/browse_search/browse_search_google

Revision             Result                  N
chromium@456905      446.551 +- 362.884      21      good
chromium@457241      765.785 +- 6003.88      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=browse.search.google system_health.common_desktop

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

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


| 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)
ref also regressed.
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Apr 11 2017


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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/browse_search/browse_search_google

Revision             Result                  N
chromium@457143      702.131 +- 3358.44      21      good
chromium@457241      755.632 +- 3252.59      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=browse.search.google system_health.common_desktop

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

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


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

Sign in to add a comment