Issue metadata
Sign in to add a comment
|
3.2% regression in speedometer at 449143:449175 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988141688784504368
,
Feb 10 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : speedometer Metric : AngularJS-TodoMVC/AngularJS-TodoMVC Revision Result N chromium@449142 4554.05 +- 227.168 21 good chromium@449175 4560.3 +- 203.499 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988141688784504368 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5833441813200896 | 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!
,
Feb 10 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tebbi@chromium.org
, Feb 9 2017