New issue
Advanced search Search tips

Issue 689842 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

14.4%-14.7% regression in tracing.tracing_with_debug_overhead at 448186:448518

Project Member Reported by lanwei@chromium.org, Feb 8 2017

Issue description

See the link to graphs below.
 

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : tracing.tracing_with_debug_overhead
  Metric       : Max number of events per second_avg/Max number of events per second_avg

Revision             Result                  N
chromium@448185      13458.5 +- 721.954      14      good
chromium@448518      15825.3 +- 5017.38      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 tracing.tracing_with_debug_overhead

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

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


| 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 Tests>AutoBisect.  Thank you!
Project Member

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


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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : tracing.tracing_with_debug_overhead
  Metric       : Max number of events per second_avg/Max number of events per second_avg

Revision             Result                  N
chromium@448185      13458.5 +- 721.954      14      good
chromium@448518      15825.3 +- 5017.38      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 tracing.tracing_with_debug_overhead

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

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


| 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