New issue
Advanced search Search tips

Issue 785741 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4% regression in speedometer at 516305:516385

Project Member Reported by bmeurer@google.com, Nov 16 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 16 2017

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=f62edee30df82a996012b6108851734af2370a023e3c3ee72cbbfc0542caf1f2


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

android-nexus7v2
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 16 2017


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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : speedometer
  Metric       : EmberJS-TodoMVC/EmberJS-TodoMVC

Revision             Result                  N
chromium@516304      7062.36 +- 531.004      21      good
chromium@516385      7062.36 +- 396.362      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 speedometer

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8962786222162010528


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Untriaged)

Sign in to add a comment