New issue
Advanced search Search tips

Issue 772777 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.2%-30.1% regression in speedometer at 507301:507303

Project Member Reported by bmeurer@google.com, Oct 9 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 9 2017 

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

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


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

android-nexus5X
chromium-rel-win7-gpu-ati
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 9 2017 


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : speedometer
  Metric       : React-TodoMVC/React-TodoMVC

Revision             Result                  N
chromium@507300      3381.01 +- 424.372      21      good
chromium@507303      3684.23 +- 2105.96      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/8966241842759534304


For feedback, file a bug with component Speed>Bisection

Comment 4 by bmeu...@chromium.org, Oct 9 2017

Status: WontFix (was: Untriaged)
►

Sign in to add a comment