New issue
Advanced search Search tips

Issue 752463 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

5.7% regression in speedometer at 491366:491473

Project Member Reported by tebbi@chromium.org, Aug 4 2017

Issue description

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

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


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

android-nexus7v2

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

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

Revision             Result                  N
chromium@491365      2488.62 +- 226.757      21      good
chromium@491473      2516.12 +- 295.678      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/8972185034245562928


For feedback, file a bug with component Speed>Bisection

Comment 4 by tebbi@chromium.org, Aug 22 2017

Status: WontFix (was: Assigned)
not reproducible

Sign in to add a comment